Magebean Logo Magebean

Magebean Documentation

Getting Started

Set up your Company, register a Magento Application and Instance, assign a required Baseline, begin the first Assessment, and connect Magebean CLI Agent.

On this page

Set up the managed Application context

Magebean begins with the Company responsible for the Magento system. Register the business-level Application, then add each deployable Instance—such as production, staging, or development—with its owner, environment, risk classification, and expected scan frequency.

Application

The business-level Magento system with ownership, criticality, data classification, exposure, and lifecycle context.

Instance

One deployable environment of that Application. Agent pairing, Scan Runs, deployment Revisions, and Assessments are associated with the Instance.

Install Magebean CLI

Download the current PHAR, keep it outside the Magento web root when practical, and verify that PHP can execute it.

curl --fail --location https://magebean.com/files/magebean.phar --output magebean.phar
php magebean.phar --version
php magebean.phar list

For source builds and the published checksum, use the Magebean CLI download page. Review the CLI invocation reference for supported commands and global options.

Run your first scan

Run the Basic profile against a Magento installation you are authorized to assess. Pass the Magento root explicitly so the target is unambiguous.

php magebean.phar \
  --path=/var/www/magento \
  --profile=basic
Use a safe environment. Begin in development, staging, or an approved maintenance context. A scan reads security-relevant state; it is not authorization to test systems outside your scope.

Understand scan results

A scan result is evidence about a rule, not the whole assessment. Interpret each outcome according to what the rule expects and what the check can observe.

Automated result
The CLI executed an observable check. A pass supports the rule; a failure identifies a gap to investigate or remediate.
Human-required verification
The rule needs review, testing, records, judgment, or evidence the CLI cannot establish reliably.
Applicability decision
A rule may be not applicable only when its condition or component is genuinely absent and the rationale is recorded.

Continue in the Security Dashboard

Create a Company-configured Baseline from a system Profile and manually assign it to the Application. Then create an independent Assessment for the selected Instance and Baseline. The Assessment snapshots its Baseline configuration; later Baseline changes do not modify it.

Pair Magebean CLI Agent with the Instance—not with an Assessment. One Instance scan may update matching automated Items in multiple relevant active Assessments. Human-required Items still need permitted user verification, and user-submitted Evidence requires independent approval.

Follow the Dashboard workflow →