For a shopper-friendly overview of features and setup, see the Magento 2 Security AI User Guide - CMS Content Risk Scanning on the storefront. This wiki page remains the full technical documentation.

This is a Toweringmedia Magento 2 extension guide for the current admin extension catalog.

• Security AI for Magento 2 (SKU tm-security-ai)

Security AI scans Magento CMS content — pages, blocks, and related files — for risky or injected markup and reports what it finds as reviewable findings. It runs on a schedule within a spend budget you set, and can alert staff when new findings appear. It is a detection and reporting tool: it surfaces problems for a human to action.

• Scheduled AI scanning of CMS pages and blocks for suspicious or injected content.
• File scanning scope options.
• Findings grid for reviewing what was detected.
• Configurable scan scope, schedule, spend budget, and alerts.

• Magento 2.4.x (Open Source or Adobe Commerce).
• PHP: ^8.1 || ^8.2 || ^8.3 || ^8.4 (as declared by the published package).
• A current Toweringmedia license and Composer credentials for https://composer.toweringmedia.com/.
• Requires toweringmedia/module-ai-core and toweringmedia/module-base — Composer installs both automatically.
• AI Core must be configured with a working AI provider and a spend budget before scans will run.

Install and validate in a staging environment before production rollout.

cd /path/to/magento
composer require toweringmedia/module-security-ai
 
bin/magento module:enable Toweringmedia_SecurityAi
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
bin/magento cache:flush

Currently published versions at the time of writing:

• toweringmedia/module-security-ai — 1.2.0

Toweringmedia packages are served from the licensed Composer repository https://composer.toweringmedia.com/. If Composer reports that the package could not be found, your credentials are missing or the license does not cover this package yet. Retrieve your keys from My Account on toweringmedia.com, or contact support@toweringmedia.com.

General installation notes that apply to every Toweringmedia extension are in the installation guide.

• Stores > Configuration > Towering Media > Content Security AI (config section toweringmedia_security_ai).
• Groups: general, schedule, scope, file_scan, budget, and alerts.
• Admin screen: Towering Media > Security & Compliance > Content Security Scan.

1. Configure AI Core first, then set the scan scope and budget in Content Security AI.
2. Run an initial scan and review the findings grid — expect some false positives on a first pass while you tune scope.
3. Set up alerts once the findings are at a level your team can act on.

• Scanning consumes AI provider spend. The budget group exists to cap that — set it before your first full scan.
• This tool reports risk. It does not remove or quarantine content on its own.

• bin/magento module:status shows the module(s) as enabled.
• Extension configuration saves without errors in Admin.
• The admin screens listed above are reachable and load without error.
• Expected storefront/admin behavior is present after a cache flush.
• No critical PHP/JS errors appear in var/log/ during the primary test flow.

• Composer cannot find the package: confirm the https://composer.toweringmedia.com/ repository and your credentials are present in auth.json, and that your license covers this package.
• Feature not visible: verify module status, flush cache, and redeploy static content.
• Admin setting not applying: clear cache and confirm the config scope (default / website / store view).
• Unexpected behavior: retest with only the required related modules enabled.

• support@toweringmedia.com
• Magento maintenance and support

• Magento 2 extension index
• Global docs home