Isaca Updated AAISM Exam Questions and Answers by andrei

AAISM prescribes Preparation as the foundational phase of AI incident response. The first priority is to form and empower a cross-functional incident response (IR) team with AI/ML expertise (security, data science, product, legal/compliance). Only once the accountable team exists can you define playbooks, communications, containment/eradication steps, recovery processes, and escalation paths. Without a designated team, procedures and channels lack ownership and effectiveness.

AAISM classifies learning paradigms by the presence of labeled targets. Creating categories (labels) and training on them is supervised learning, where input features are mapped to known outputs and optimization minimizes prediction error against ground truth. Unsupervised (B) discovers structure without labels; reinforcement (A) optimizes behavior via rewards; “machine learning” (C) is the broad field, not the specific technique.

The data Preparation phase—covering sourcing, collection, labeling, cleansing, and provenance—presents the greatest inherent risk because it is where privacy, consent, representativeness, bias, quality, lineage, and legality must be established. Decisions and defects here propagate into training and downstream use, amplifying ethical, regulatory, and accuracy risks.

While Training can introduce additional risks (e.g., poisoning, leakage), these are frequently mitigated by controls that depend on having trustworthy prepared data. Monitoring and Maintenance are later-life-cycle phases oriented toward detection and correction; they are critical but inherently rely on the foundation set during Preparation.

For generative AI, the primary enterprise security exposure is data and content exfiltration or policy violations at output, including leakage of sensitive data, toxic content, or regulatory non-compliance. AAISM prescribes policy-aligned output monitoring (e.g., DLP checks, PII/PHI detection, toxicity/safety filters, watermark/attribution checks) integrated into inference gateways to enforce organizational policies and evidence compliance. Exceeding benchmarks (A) is not a control; training-data validation (C) may be infeasible with third-party LLMs; and kill switches (D) are essential contingency controls but do not continuously strengthen everyday security posture.