====== Security AI for Magento 2 User Guide ======

===== Related overview =====

For a shopper-friendly overview of features and setup, see the [[https://toweringmedia.com/magento-2-security-ai-user-guide|Magento 2 Security AI User Guide - CMS Content Risk Scanning]] on the storefront. This wiki page remains the full technical documentation.

===== Extension context =====

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

===== Product page =====

  * [[https://toweringmedia.com/security-ai-for-magento-2|Security AI for Magento 2]] (SKU ''tm-security-ai'')

===== Overview =====

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.

===== What this extension does =====

  * 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.

===== Requirements =====

  * 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.

===== Installation =====

Install and validate in a staging environment before production rollout.

<code bash>
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
</code>

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 [[mailto:support@toweringmedia.com|support@toweringmedia.com]].

General installation notes that apply to every Toweringmedia extension are in the [[https://toweringmedia.com/installation|installation guide]].

===== Configuration =====

  * 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**.

===== Basic usage and what to expect =====

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

===== Notes and limitations =====

  * 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.

===== Validation checklist =====

  * ''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.

===== Troubleshooting =====

  * **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 =====

  * [[mailto:support@toweringmedia.com|support@toweringmedia.com]]
  * [[https://toweringmedia.com/magento-maintenance-support|Magento maintenance and support]]

===== Related Magento 2 docs =====

  * [[magento2:extensions:start|Magento 2 extension index]]
  * [[start|Global docs home]]