ISACA
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…
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…
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…
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…
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…
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…
ISACA AAISM: Governing AI Security Risk
Governing AI security risk means deciding which AI-related exposures matter to the enterprise, how much risk the organization is willing to accept, which controls are proportionate, and who has authority to make those decisions. It is broader than securing a model. The risk can come from data, identity, providers, human use, autonomy, business process design, regulatory obligations, or concentration on a small number of external platforms. The topic is the risk-management core of Enterprise AI Governance. In the current AAISM exam outline, AI risk management covers assessment, thresholds, treatment, threats,…
ISACA AAISM: Controls for Enterprise AI Systems
Controls for enterprise AI systems should protect the entire application path, not only the model endpoint. A production AI service combines identity, data, prompts, retrieval, model providers, tools, memory, APIs, deployment pipelines, monitoring, and human decisions. Each layer can introduce risk, and a safeguard in one layer cannot compensate for every weakness in another. The control model belongs inside Enterprise AI Governance and maps directly to the current AAISM exam emphasis on AI security architecture, lifecycle controls, data management, privacy, trust and safety, monitoring, and risk-based human oversight. The practical…
ISACA AAISM: AI Model Risk for Security Leaders
An AI model can become a security risk even when it never suffers a conventional software exploit. Sensitive training data may be memorized, a retrieval system may disclose information across tenants, a model or prompt can be manipulated, and an automated action can reach a system it should not control. Security leaders therefore need an AI model risk record that connects technical behavior to business impact. ISACA’s AAISM exam outline covers AI governance, AI risk management and AI technologies and controls; the following method translates those themes into practical review….
ISACA AAISM: AI Incident Response Governance
AI incident response governance defines how an organization makes accountable decisions when an artificial-intelligence system creates, amplifies, or participates in a security incident. The technical response may involve disabling an endpoint or revoking a credential, but governance determines who can take that action, which evidence must be preserved, when customers or regulators are notified, how business continuity is protected, and what must be proven before the system returns to service. The topic sits naturally inside Enterprise AI Governance. ISACA’s current AAISM exam outline explicitly includes AI-specific incident investigation, documentation, reporting,…
ISACA CISM: Security Governance That Drives Decisions
Security governance establishes who sets information-protection objectives, who makes risk decisions, how security performance is assessed and what happens when a business unit wants an exception. It is not merely a collection of technical policies. ISACA CISM emphasizes aligning the information security strategy with enterprise goals, legal requirements, organizational culture and stakeholder accountability. ISACA has announced a CISM exam-outline change effective November 3, 2026. On October 25 the current outline still governs earlier sittings, while revised material is being prepared for the forthcoming version. Governance questions in either version require…
ISACA CISM: Risk Appetite and Security Priorities
Risk appetite describes the kinds and levels of uncertainty an enterprise is willing to pursue or retain while meeting its objectives. It does not mean a security team can ignore a known weakness because it has a low severity score. In CISM practice, security managers translate organizational appetite into risk decisions for critical services, investments, suppliers and exceptions. The business owns the risk; the security function supplies analysis, controls and credible alternatives. Home/ISACA/ISACA CISM: Risk Appetite and Security PrioritiesISACAPublished October 7, 2026On this pageDistinguish appetite, tolerance and operating thresholdsAssess exposure…
ISACA CISM: Measuring Security Program Performance
Information security programs can generate thousands of metrics without proving that they reduce business risk. Counting blocked attacks, completed training sessions or devices running an endpoint agent describes activity; it does not necessarily show whether critical services are becoming safer. An ISACA CISM security manager needs measures that connect program objectives, control performance, residual risk and executive decisions. Home/ISACA/ISACA CISM: Measuring Security Program PerformanceISACAPublished October 7, 2026On this pageStart with outcomes and risk hypothesesDifferentiate coverage, effectiveness and outcomesUse leading indicators and lagging indicators togetherBuild a decision-oriented executive scorecardMeasure supplier and…
ISACA CISM: Incident Management at Executive Level
Major security incidents become executive decisions when they threaten customer trust, continuity, legal obligations or the organization’s ability to operate. A security manager must connect technical containment with business priorities: what is affected, who can authorize disruptive action, which stakeholders must be informed and how the organization knows that recovery is safe. That is the focus of incident management at the leadership level in ISACA’s Certified Information Security Manager (CISM) practice. Incident management is an established CISM domain, but the exam outline is changing. As of October 25, 2026, ISACA’s…
Enterprise AI Governance
Enterprise AI Governance is the management system that decides where artificial intelligence may be used, which risks require treatment, who owns those risks, and what evidence proves that controls continue to work. It sits above individual models and applications. A model can be technically strong and still create unacceptable exposure if the organization has weak data ownership, unclear accountability, unmanaged vendors, poor incident escalation, or no method for deciding when human oversight is mandatory. Home/ISACA/Enterprise AI GovernanceISACAPublished October 7, 2026On this pageDefine accountable AI ownershipUse risk tiers instead of one…