Data lineage records and monitors the end-to-end journey of data-sources, movements, transformations, storage locations, uses, and dependencies-providing traceability, auditability, and accountability across the AI lifecycle. "Origin" is a single point (provenance), "transformation" is one step within the flow, and
"processing" is a general activity rather than a governance record of the entire path.
References: AI Security Management (AAISM) Body of Knowledge: Data Governance-Provenance and Lineage; AAISM Study Guide: Lineage Documentation, Traceability, and Audit Evidence.

Training detection models on relevant, representative historical data improves signal quality, reduces false positives, and automates triage-directly lowering human workload and error rates (e.g., alert fatigue, missed correlations). Penetration testing is valuable but episodic and does not systematically reduce day-to-day operator error. "Ensure responsible use" is a governance aim, not a concrete method to cut human error in detection. Manual monitoring increases reliance on human judgment and is prone to inconsistency.
References: AI Security Management (AAISM) Body of Knowledge: Model Development & Evaluation Controls; Data Selection and Representativeness; Operationalization to Reduce Human Error. AAISM Study Guide: Tuning Detection Systems with Historical Corpora; Alert Quality, Precision/Recall, and SOC Workflow Integration.

When an AI system experiences an attack after being in production for an extended period, the most effective mitigation strategy is to update the deployed training data with new adversarial data. This process strengthens the model's resilience by retraining it to recognize and resist attack vectors that were previously unknown or unaccounted for. According to the AI Security Management™ (AAISM) framework, risk mitigation for AI systems must address model robustness through adversarial retraining, data quality improvement, and model lifecycle hardening rather than relying solely on reactive measures.
Why Option B is Correct:
* Incorporating adversarial examples into the training set enhances the system's ability to correctly classify and withstand malicious inputs.
* This approach directly mitigates the vulnerability exploited in the attack and supports a proactive, continuous risk management cycle.
Why Other Options Are Incorrect:
* Option A: Monitoring helps detect suspicious activity but does not resolve the underlying vulnerability.
* Option C: Concealing confidence scores may reduce model transparency but does not address the attack mechanism or its root cause.
* Option D: Implementing access controls protects the model's architecture but does not improve model robustness against input manipulation attacks.
Exact Extract from Official AAISM Study Guide:
"AI risk management requires continuous improvement following incidents. After an adversarial or data poisoning event, the preferred risk treatment involves retraining the model using adversarial data and updated datasets to enhance robustness. This ensures the AI model adapts to evolving threat landscapes rather than merely restricting access or obscuring outputs." References:
AI Security Management™ (AAISM) Body of Knowledge: AI Risk Treatment and Mitigation Strategies, Adversarial Robustness and Resilience Engineering.
AI Security Management™ Study Guide: Model Lifecycle Security, Continuous Risk Treatment through Adversarial Retraining.
ISO/IEC 23894:2023, Clause 8.3.2 - Risk treatment through robustness improvement and adversarial data inclusion.

AAISM directs organizations to embed security, safety, and compliance controls at design time ("secure-by- design" and "shift-left"), ensuring requirements for robustness, privacy, and governance are defined as non- functional constraints on architecture, data sourcing, model choices, and evaluation criteria before any model is trained. Deferring these requirements to training, testing, or deployment increases residual risk and rework, and weakens traceability of control coverage.
References:* AI Security Management™ (AAISM) Body of Knowledge: Governance-Secure-by-Design; Policy-to-Control Traceability; Requirements Management* AAISM Study Guide: AI Program Lifecycle- Planning & Design Controls; Design-time Threat Modeling and Control Selection* AAISM Mapping to Standards: Design-phase Risk Identification and Requirements Engineering for AI

AAISM identifies executive sponsorship and senior management buy-in as the foremost success factor for AI initiatives. It secures resources, resolves cross-functional conflicts, sets risk appetite, and enforces adherence to governance and controls. Model cards (A), risk registers (B), and lifecycle data mapping (C) are vital practices within the program, but without top-level commitment, adoption, funding, and accountability often fail.
References: AI Security Management (AAISM) Body of Knowledge - AI Program Governance; Executive Sponsorship & Accountability; Strategy-to-Control Alignment for Successful AI Delivery.