Practice Exams:

Governance & Compliance

ACAMS CAMS: Writing Useful Suspicious Activity Reports

A suspicious activity report is not the place to reproduce an investigation file verbatim. Its job is to give the receiving authority a clear, concise, fact-based explanation of the suspicious activity and the context needed to understand why it matters. The narrative should help a reader reconstruct the pattern without guessing which transactions or relationships drove the decision. Home/ACAMS/ACAMS CAMS: Writing Useful Suspicious Activity ReportsACAMSPublished October 7, 2026On this pageOpen with the reason for suspicionUse chronology to make complex activity readableExplain relationships among subjects and accountsDescribe why normal explanations were…

Read More

ACAMS CAMS: Transaction Monitoring Alert Triage

Transaction-monitoring alerts are the beginning of an anti-money-laundering investigation, not evidence that a customer committed a crime. Rules, scenarios, and analytics identify activity that might depart from expected behavior; analysts must then establish what happened, why the behavior matters, and whether it can be reasonably explained. The quality of that work depends on customer information, transaction reconstruction, investigative judgment, and documentation. A useful triage process separates routine anomalies from patterns requiring escalation without treating speed or a low alert count as proof of good compliance. Define what the alert actually…

Read More

ACAMS CAMS: Sanctions Screening False Positives

Sanctions screening systems deliberately cast a wide net. Names can be transliterated in multiple ways, data can be incomplete, aliases can overlap with ordinary customers, and automated matching must tolerate spelling and formatting differences. The result is a recurring operational problem: many alerts that resemble a listed party but are not true matches. Within AML operations, false positives are not merely an efficiency issue. Excessive noise consumes analyst time, delays onboarding or payments, and can hide important cases in a large queue. The goal is to reduce predictable noise without…

Read More

ACAMS CAMS: Risk-Based AML Programs in Practice

A risk-based AML program is built around a simple idea: not every customer, product, geography, transaction, or delivery channel creates the same exposure. The difficult part is turning that idea into consistent operating decisions. Institutions need a documented way to identify risk, rank it, apply proportionate controls, monitor whether those controls work, and adjust when new evidence changes the picture. Home/ACAMS/ACAMS CAMS: Risk-Based AML Programs in PracticeACAMSPublished October 7, 2026On this pageSeparate inherent risk from control effectivenessUse customer risk to determine due-diligence depthRisk segmentation improves monitoring qualitySanctions controls need their…

Read More

ACAMS CAMS: Customer Due Diligence Beyond Checklists

Customer due diligence is often implemented as a sequence of forms, identity checks, ownership questions, and approval fields. Those steps are necessary, but the real purpose is to build a defensible understanding of who the customer is, why the relationship exists, what activity should be expected, and what risk factors deserve continued attention. A completed checklist without that understanding creates the appearance of control without the substance. Home/ACAMS/ACAMS CAMS: Customer Due Diligence Beyond ChecklistsACAMSPublished October 7, 2026On this pageBegin with the purpose of the relationshipIdentity and ownership need verification proportional…

Read More

ISACA CISA: Testing Access Controls in an Audit

Access-control audits fail when they treat identity as a list of accounts instead of a lifecycle of authorization decisions. An effective test asks who received access, why it was granted, how privileges changed as responsibilities changed, what technical enforcement exists, and whether the organization can remove access when the business justification ends. The current CISA scope places identity and access management within protection of information assets while audit execution includes sampling, evidence collection, analytics, and reporting. Within security governance, those disciplines come together in a test that connects entitlement data…

Read More

ISACA CISA: Reporting Audit Findings Clearly

A useful IT audit finding tells management what condition was observed, which criterion it failed, why that matters and what action can reasonably reduce the risk. Reporting is not the same as reproducing fieldwork notes. An audit report should help decision-makers understand a control weakness well enough to assign ownership and verify remediation. For CISA preparation, connect reporting to the evidence gathered during planning and testing. ISACA emphasizes professional judgment and reliable audit evidence; conclusions should be proportionate to what the audit actually demonstrated. Use a finding structure that supports…

Read More

ISACA CISA: IT Audit Scoping That Finds Real Risk

Audit scoping is where much of an engagement’s value is decided. A scope that is too broad produces shallow checklist coverage, while a scope that is too narrow can miss the dependency or control boundary where the material risk actually sits. Risk-based scoping creates a defensible connection between business objectives, technology, threats, control history, and the work the audit team will perform. Home/ISACA/ISACA CISA: IT Audit Scoping That Finds Real RiskISACAPublished October 7, 2026On this pageStart from business services and material dataUse risk to prioritize depthInclude the control chain, not…

Read More

ISACA CISA: Evidence Quality in IT Audits

An audit conclusion is only as strong as the evidence supporting it. Large quantities of screenshots, exported reports, policy documents, and interview notes can create the appearance of rigor while still failing to prove that a control operated as described across the relevant period and population. Within Security Governance & Assurance, evidence quality depends on relevance, reliability, completeness, timing, source, and the relationship between the artifact and the audit objective. The auditor should know what claim each piece of evidence supports and what uncertainty remains after reviewing it. Good evidence…

Read More

ISACA CISA: Auditing Cloud Environments

Cloud audits are difficult when reviewers treat the cloud as either someone else’s infrastructure or a long list of provider settings. The audit has to connect the provider’s control environment with the customer’s architecture, identity model, data handling, configuration, monitoring, and resilience responsibilities. Within Security Governance & Assurance, the first task is to identify the business services and data that depend on the cloud environment. Only then can the auditor decide which shared-responsibility boundaries, technical controls, provider attestations, and operational practices are relevant to the risk being assessed. A useful…

Read More

ISACA CISA: Auditing Change Management

Change management is designed to let organizations modify production systems without turning every release into an uncontrolled experiment. An audit therefore needs to evaluate more than whether a request was logged. It should test whether changes are authorized, assessed, implemented, reviewed, and recoverable in a way that preserves business service objectives. Within Security Governance & Assurance, change is a control chain that connects governance, development, operations, incident response, and business ownership. A technically successful deployment can still represent a control failure if it bypassed approval, lacked testing, or introduced risk…

Read More

IAPP AIGP: Managing Third-Party AI Risk

Third-party AI risk is difficult because the organization depends on a system it does not fully control. A vendor can change models, subprocessors, security controls, training practices, pricing, retention, geographic processing, or service limits while the customer continues to depend on the same business workflow. Governance therefore has to manage both the AI behavior and the dependency relationship. Home/IAPP/IAPP AIGP: Managing Third-Party AI RiskIAPPPublished October 7, 2026On this pageMap the dependency before scoring the vendorDecide what evidence is necessaryContract for the controls that matterControl what data reaches the providerPlan for…

Read More

IAPP AIGP: Data Governance for AI Systems

AI governance is often discussed as model governance, but many production failures originate in the data around the model. Training datasets, evaluation sets, retrieval indexes, prompts, user feedback, tool outputs, logs, and generated records all have different owners, permissions, retention needs, and quality expectations. Data governance gives the organization a way to manage those differences across the AI lifecycle. Home/IAPP/IAPP AIGP: Data Governance for AI SystemsIAPPPublished October 7, 2026On this pageClassify data by role in the AI systemAssign owners and stewards to real decisionsPreserve lineage from source to outputTreat quality…

Read More