Set the store scope
Start with the storefronts and environments your team owns.
Your store runs on code.
Keep a closer watch.
Keep track of your modules, checkout scripts, and customer APIs. See what changed, and what needs attention.
Early access. Join the list for the first release.
Modules & extensionsCheckout changesStore APIs
Magento security, in one place.
Product concept for the upcoming integration. Illustrative data.
Planned coverage
Your custom store. Its specific risks.
We’re building for the extensions, storefronts, and integrations that make a Magento installation your own.
Keep your extensions in view.
Track changes to connected modules and storefront assets. Compare a new release with the baseline your team approved.
- Changes to monitored module files
- Unexpected storefront code
- Findings linked to the responsible component
Example signalReview
A module changed outside the baseline.
app/code/Harbor/Checkout- Before
- Approved module snapshot
- Observed
- Frontend asset modified
Review the module diff alongside your most recent deployment.
Illustrative example · Synthetic dataCheck what changed at checkout.
Watch the scripts and destinations introduced by checkout customizations. Give your team a specific change to investigate.
- New third-party checkout scripts
- Unexpected script destinations
- Changes across connected store views
Example signalReview
A checkout component loads a new script.
Harbor/Checkout/view/frontend/web/js/checkout.js- Before
- Approved checkout sources
- Observed
- External host: unexpected.test
Inspect the new source before restoring or approving the component.
Illustrative example · Synthetic dataCheck access beyond the storefront.
Use test identities to review the boundaries around customer APIs and custom integrations, within an agreed scope.
- Customer data exposed across accounts
- Custom endpoint authorization
- Integration permissions and role boundaries
Example signalReview
A restricted action accepts a customer token.
POST /rest/V1/harbor/customer-export- Before
- Expected: authorized operator only
- Observed
- Customer test account accepted
Apply the required permission on the server and rerun the control check.
Illustrative example · Synthetic dataKeep the release moving. Keep the evidence.
The workflow we’re building, from a defined scope to useful evidence.
Connect the context
Add supported components and dedicated test identities when early access opens.
Check after changes
Review the finding, apply the fix, and retest the affected flow.
Early accessGet a note
Get a note
when it’s ready.
Leave your email for rootscan for Magento. Add your store URL so we know what you’re building on.
Product updates, when there’s news.No store credentials needed.
Need app testing today? Get early access
We’ll let you know when it’s ready.
Before you
get started.
A few details, in plain language.
Is the Magento product available yet?
It is coming soon. The early-access list is open; the page and product views show the planned experience.
Will it support Adobe Commerce too?
Share your edition, version, and storefront setup when registering interest. Supported configurations for Magento Open Source and Adobe Commerce will be confirmed before access opens.
How does this fit with Adobe’s Security Scan Tool?
Use the checks and security tools already available for your installation. rootscan is being designed to add connected component context and authenticated application checks; it does not replace platform maintenance.
What about multiple stores or a headless storefront?
Include the relevant domains and frontend setup in your request. Each environment needs a defined scope, and compatibility will be confirmed during early access.
What will it cost?
Magento pricing has not been announced. Joining the list does not start a subscription.
