Security Governance & Audit
CompTIA SY0-701: Change Management and Security Impact
Learn SY0-701 change management through documentation, version control, security impact analysis, approvals, dependencies, testing, backout plans, maintenance windows, emergency change, unauthorized-change detection, and post-change validation.
CompTIA SY0-701: Governance, Third-Party Risk, and Compliance
Learn SY0-701 governance through policies, risk decisions, third-party and supply-chain risk, compliance, audits, and security awareness.
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…
ISC2 CISSP: Software Supply Chain Risk for CISSPs
Modern applications depend on code, packages, build systems, hosted services, signing keys, maintainers, and delivery platforms that may be controlled by different organizations. A vulnerability in a dependency is one risk; a compromised package publisher, stolen build token, tampered artifact, or malicious update is another. Software supply chain security asks whether an organization can establish what it is running, where it came from, which parties were trusted, and how it will respond if any of those assumptions fail. Home/ISC2/ISC2 CISSP: Software Supply Chain Risk for CISSPsISC2Published October 7, 2026On this…
ISC2 CISSP: Security Models Beyond Memorization
Security models matter when they help engineers and leaders reason about what information is allowed to flow, which subject may act on which object, and what property the system is trying to preserve. Memorizing labels such as Bell-LaPadula or Biba without understanding the problem each model addresses misses their practical value. The models are abstractions that make security assumptions explicit. Home/ISC2/ISC2 CISSP: Security Models Beyond MemorizationISC2Published October 7, 2026On this pageBegin with the property being protectedUse Bell-LaPadula to reason about confidentialityUse Biba to reason about integrityThink about conflict of interest…
ISC2 CISSP: Security Leadership Across Eight Domains
A security leader rarely gets to choose between security and no security. The real choice is which risks to reduce, which obligations must be met, which controls are proportionate, and what evidence shows the program is working. Those choices span technology, people, vendors, legal responsibilities, and business continuity. Treating security leadership as an inventory of tools hides the accountability that makes the controls useful. Home/ISC2/ISC2 CISSP: Security Leadership Across Eight DomainsISC2Published October 7, 2026On this pageStart with business outcomes and explicit risk ownershipConnect each CISSP domain to a leadership decisionGovern…
ISC2 CISSP: Privacy Engineering for Security Leaders
Privacy engineering for security leaders turns privacy requirements into technical and operational decisions that can be implemented, tested, and monitored. Privacy and security overlap, but they are not identical. A system can be well protected from attackers and still collect too much data, retain it too long, use it for an unexpected purpose, or make it difficult to honor an individual’s rights. Home/ISC2/ISC2 CISSP: Privacy Engineering for Security LeadersISC2Published October 7, 2026On this pageSeparate privacy from security without separating the teamsMap data before designing controlsMinimize collection and propagationBuild access around…
ISC2 CISSP: Physical Security in Hybrid Workplaces
Physical security is easy to overlook in cloud-centered workplaces because the most visible controls are identity policies, encryption, and network segmentation. Yet devices can be stolen, confidential conversations overheard, visitors admitted into restricted spaces, and infrastructure damaged by environmental failures. Hybrid work increases the number of places in which people handle sensitive information; it does not eliminate responsibility for physical safeguards. Home/ISC2/ISC2 CISSP: Physical Security in Hybrid WorkplacesISC2Published October 7, 2026On this pageMap assets to places and responsible partiesUse layered controls matched to threat and siteMake visitor and staff access…
ISC2 CISSP: Cryptographic Key Management at Scale
Encrypting sensitive data does not make it safe if encryption keys can be copied, misused, lost, or silently replaced. In large organizations, keys often cross application teams, cloud services, geographic regions, automation pipelines, backup environments, and outsourced systems. The hardest design problem is therefore not selecting a strong cipher in isolation. It is making every key’s purpose, ownership, access, rotation, recovery, and retirement traceable without disrupting the systems that depend on it. Home/ISC2/ISC2 CISSP: Cryptographic Key Management at ScaleISC2Published October 7, 2026On this pageInventory keys by purpose and impactGenerate and…
ISC2 CISSP: Business Continuity Without Paper Plans
Business continuity is not proved by possessing a plan. It is proved when an organization can keep essential outcomes available—or restore them within agreed limits—after the assumptions in that plan fail. A cloud outage, unavailable identity provider, ransomware incident, power loss, or critical supplier failure can expose dependencies that looked insignificant on paper. Effective continuity work translates business impact into operational priorities and tests whether real people, systems, facilities, and partners can meet those priorities. Home/ISC2/ISC2 CISSP: Business Continuity Without Paper PlansISC2Published October 7, 2026On this pageBegin with an impact…