🇺🇸 CompTIA Security+ · subject

CompTIA Security+ Security Program Management and Oversight Syllabus

The Security Program Management and Oversight syllabus for CompTIA Security+ in full: 5 chapters, 23 topics and 45 sub-topics, every one listed below, plus 71 Security Program Management and Oversight flashcards with answers.

5Chapters
23Topics
45Sub-topics
71Flashcards

Security Program Management and Oversight syllabus: all 5 chapters

Expand any chapter to see its topics and sub-topics.

  1. Security Governance

    5 topics
    • Guidelines, Policies, and Standards
      • Acceptable use policy (AUP)
      • Information security and business continuity policies
      • Password, access control, and encryption standards
    • Procedures
      • Change management and onboarding/offboarding
      • Playbooks
    • Governance Structures
      • Boards, committees, government entities
      • Centralized vs decentralized governance
    • Roles and Responsibilities
      • Owners and controllers
      • Processors and custodians/stewards
    • External Considerations
      • Regulatory, legal, industry, and geographic
      • Local/regional, national, global
  2. Risk Management

    5 topics
    • Risk Identification and Assessment
      • Risk assessment types: ad hoc, recurring, one-time, continuous
      • Risk register, key risk indicators, risk owners, risk threshold
    • Risk Analysis
      • Qualitative and quantitative
      • SLE, ALE, ARO
      • Probability, likelihood, exposure factor, impact
    • Risk Tolerance and Appetite
      • Expansionary, conservative, neutral appetite
    • Risk Management Strategies
      • Transfer and accept (exemption/exception)
      • Avoid and mitigate
    • Business Impact Analysis
      • RTO and RPO
      • MTTR and MTBF
  3. Third-Party Risk Management

    4 topics
    • Vendor Assessment
      • Penetration testing and right-to-audit clause
      • Independent assessments and supply chain analysis
    • Vendor Selection
      • Due diligence and conflict of interest
    • Agreement Types
      • SLA, MOA, MOU
      • MSA, SOW, NDA, BPA
    • Vendor Monitoring and Questionnaires
  4. Security Compliance and Audits

    5 topics
    • Compliance Reporting
      • Internal and external reporting
    • Consequences of Non-Compliance
      • Fines and sanctions
      • Reputational damage and loss of license
    • Compliance Monitoring
      • Due diligence/care and attestation
      • Internal and external monitoring, automation
    • Privacy
      • Legal implications: local/regional, national, global
      • Data subject, controller, processor
      • Right to be forgotten
    • Audits and Assessments
      • Internal: compliance, audit committee, self-assessment
      • External: regulatory, examinations, attestation
      • Penetration testing: known/partially known/unknown environment
  5. Security Awareness

    4 topics
    • Phishing Awareness
      • Campaigns and recognizing phishing attempts
      • Responding to suspicious messages
    • Anomalous Behavior Recognition
      • Risky, unexpected, and unintentional behavior
    • User Guidance and Training
      • Policy/handbooks and situational awareness
      • Insider threat, password management, social engineering
      • Operational security and remote/hybrid work
    • Awareness Program Development and Execution
      • Reporting and monitoring
      • Development and execution

CompTIA Security+ Security Program Management and Oversight flashcards — 71 questions with answers

  1. What is the difference between a policy, a standard, a procedure, and a guideline in a security governance hierarchy?

    Policy = high-level management statement of intent (the 'why/what', mandatory). Standard = specific mandatory requirements that enforce a policy (the 'what', e.g., AES-256). Procedure = step-by-step instructions to implement (the 'how', mandatory). Guideline = recommended, non-mandatory best practices.

  2. What is an Acceptable Use Policy (AUP)?

    A document that defines the permitted and prohibited uses of an organization's systems, networks, and data by employees, contractors, and other users.

  3. In security governance, why are standards considered mandatory while guidelines are not?

    Standards specify uniform, enforceable requirements that ensure consistency and compliance with policy, so they must be followed. Guidelines are discretionary recommendations that offer flexibility on how to act when no rigid rule applies.

  4. Name common security policy types tested on Security+ that govern personnel and operations.

    Acceptable Use Policy (AUP), Information Security Policy, Business Continuity Policy, Disaster Recovery Policy, Incident Response Policy, Software Development Lifecycle (SDLC) Policy, and Change Management Policy.

  5. What is the purpose of a change management procedure in security operations?

    To control modifications to systems in a structured way—approval, testing, documentation, and rollback planning—so changes don't introduce vulnerabilities, outages, or unauthorized configurations.

  6. What is an onboarding versus offboarding procedure?

    Onboarding = provisioning new users with accounts, access, equipment, and policy acknowledgment. Offboarding = revoking access, recovering assets, disabling accounts, and conducting exit processes when a user leaves.

  7. What is a governance structure, and what are the main types?

    The framework defining how security decisions are made and who is accountable. Types include boards, committees, government entities, and centralized vs. decentralized governance.

  8. Compare centralized and decentralized governance structures.

    Centralized governance concentrates decision-making in one authority/team, giving consistency and tighter control. Decentralized governance distributes decision-making across units/regions, giving flexibility and local responsiveness but less uniformity.

  9. What is the role of a board of directors versus a committee in security governance?

    A board provides top-level oversight, sets strategic direction, and is ultimately accountable. A committee is a smaller specialized group that focuses on specific areas (e.g., risk or audit) and reports to the board.

  10. In data governance, what does a data owner do versus a data custodian?

    The data owner is a senior/business role accountable for classifying data and approving access. The data custodian (typically IT) handles technical protection—storage, backups, access enforcement, and maintenance—on the owner's behalf.

  11. What is the role of a data processor versus a data controller under privacy frameworks?

    The data controller determines the purposes and means of processing personal data (decides why/how). The data processor processes data on behalf of and under the instructions of the controller.

  12. What is a Data Protection Officer (DPO)?

    A designated role responsible for overseeing an organization's data protection strategy and ensuring compliance with privacy regulations such as the GDPR.

  13. What are 'external considerations' that influence a security governance program?

    Regulatory, legal, industry, and geographic/jurisdictional factors—laws and regulations, national/territory/local requirements, and industry-specific standards—that an organization must account for when designing its program.

  14. What is the difference between regulatory and contractual compliance obligations?

    Regulatory compliance is mandated by laws/regulations (e.g., HIPAA, GDPR) with legal penalties. Contractual compliance arises from agreements with other parties (e.g., PCI DSS, SLAs) and is enforced through the contract terms.

  15. What are the four primary steps/phases of the risk management process?

    1) Risk identification, 2) Risk assessment/analysis, 3) Risk response/treatment, and 4) Risk monitoring and review (ongoing).

  16. What is risk identification?

    The process of discovering and documenting potential threats, vulnerabilities, and risks that could affect organizational assets, before they can be assessed and treated.

  17. Differentiate qualitative and quantitative risk analysis.

    Qualitative analysis uses subjective ratings (e.g., low/medium/high, probability x impact matrices) without precise dollar values. Quantitative analysis uses numeric/monetary values and formulas (SLE, ARO, ALE) to calculate expected loss.

  18. Define SLE, ARO, and ALE and give the formula linking them.

    SLE (Single Loss Expectancy) = cost of one occurrence. ARO (Annualized Rate of Occurrence) = expected occurrences per year. ALE (Annualized Loss Expectancy) = SLE x ARO.

  19. How is Single Loss Expectancy (SLE) calculated?

    SLE = Asset Value (AV) x Exposure Factor (EF), where EF is the percentage of asset value lost in a single incident.

  20. Calculate ALE: an asset worth $50,000 has a 20% exposure factor and the event occurs twice per year.

    SLE = $50,000 x 0.20 = $10,000. ALE = SLE x ARO = $10,000 x 2 = $20,000 per year.

Show the other 51 Security Program Management and Oversight flashcards
  1. What is the Exposure Factor (EF) in quantitative risk analysis?

    The percentage of an asset's value that would be lost if a specific threat materialized (expressed as a decimal in the SLE formula).

  2. What is the difference between risk appetite and risk tolerance?

    Risk appetite is the broad amount/type of risk an organization is willing to pursue or accept to meet its objectives. Risk tolerance is the acceptable variation/deviation around that appetite for a specific risk.

  3. Name the three risk appetite postures organizations may adopt.

    Expansionary (willing to take greater risk for greater reward), Conservative (minimizing risk, prioritizing safety/stability), and Neutral (balanced, moderate approach).

  4. List the four primary risk management (treatment) strategies.

    Risk acceptance, risk avoidance, risk mitigation (reduction), and risk transference (sharing, e.g., insurance).

  5. What is risk transference, and give an example?

    Shifting the financial impact of a risk to a third party. Example: purchasing cybersecurity insurance or outsourcing a function so the provider bears the risk.

  6. What is risk avoidance versus risk mitigation?

    Risk avoidance eliminates the risk entirely by not engaging in the risky activity. Risk mitigation reduces the likelihood or impact of a risk using controls but does not eliminate it.

  7. What is residual risk?

    The risk that remains after security controls and mitigation measures have been applied.

  8. What is risk acceptance, and what is an 'exemption' or 'exception' in that context?

    Risk acceptance is choosing to take no action and bear a risk because it falls within tolerance or treatment costs too much. An exception/exemption is a documented, approved decision to deviate from a policy/standard and accept the associated risk.

  9. What is a risk register?

    A central document that records identified risks along with their description, likelihood, impact, owner, risk score, and mitigation/treatment plans.

  10. What do 'inherent risk' and 'control risk' mean?

    Inherent risk is the level of risk before any controls are applied. Control risk reflects the chance that existing controls fail to prevent or detect a problem.

  11. What is KRI (Key Risk Indicator) and how does it relate to risk reporting?

    A KRI is a metric that signals increasing risk exposure (early warning). Risk owners and risk reporting use KRIs to track whether risks are approaching tolerance thresholds.

  12. What is a Business Impact Analysis (BIA)?

    A process that identifies critical business functions and analyzes the operational and financial effects of their disruption to prioritize recovery.

  13. Define RTO, RPO, MTD, and MTTR.

    RTO (Recovery Time Objective) = max acceptable downtime to restore a function. RPO (Recovery Point Objective) = max acceptable data loss measured in time. MTD (Maximum Tolerable Downtime) = absolute limit a function can be down. MTTR (Mean Time To Repair) = average time to restore a failed component.

  14. What is the difference between MTBF and MTTR?

    MTBF (Mean Time Between Failures) measures the average operational time between failures (reliability). MTTR (Mean Time To Repair/Recover) measures the average time required to fix a failed system (maintainability).

  15. How does RPO drive backup strategy?

    RPO defines the maximum tolerable data loss in time, so backups must run at least as frequently as the RPO window (e.g., a 1-hour RPO requires backups/replication at least hourly).

  16. What is a vendor/supply chain assessment?

    The process of evaluating a third party's security posture, financial stability, reputation, and risk before and during a business relationship, often using audits, questionnaires, and penetration testing.

  17. Differentiate a right-to-audit clause and an independent (third-party) assessment in vendor assessment.

    A right-to-audit clause is a contractual provision letting you audit the vendor directly. An independent/third-party assessment relies on an external auditor's report (e.g., SOC 2) to evaluate the vendor's controls.

  18. What factors are considered during vendor selection?

    Due diligence (financial health, reputation, security posture) and conflict-of-interest checks to ensure no relationships compromise objectivity or create bias.

  19. What is due diligence versus due care in vendor management?

    Due diligence is the investigation/research done before entering a relationship (verifying the vendor is trustworthy). Due care is the ongoing reasonable effort and prudence exercised to protect assets during the relationship.

  20. Define SLA, MOU/MOA, and BPA agreement types.

    SLA (Service Level Agreement) = guarantees service performance metrics (uptime, response). MOU/MOA (Memorandum of Understanding/Agreement) = a non-binding/less formal statement of intent between parties. BPA (Business Partners Agreement) = defines responsibilities, profit sharing, and terms between business partners.

  21. What is a Master Service Agreement (MSA) and how does it relate to an SOW?

    An MSA is an overarching contract establishing general terms governing the relationship. An SOW (Statement of Work) is a specific document defining the deliverables, scope, timeline, and tasks for a particular project under the MSA.

  22. What is an NDA, and what does an SLA's penalty clause do?

    An NDA (Non-Disclosure Agreement) legally binds parties to keep shared confidential information secret. An SLA penalty/remedy clause specifies consequences (e.g., service credits) when the provider fails to meet agreed performance levels.

  23. What is vendor monitoring, and what tools support it?

    The ongoing evaluation of a vendor's performance, security posture, and compliance throughout the relationship—supported by questionnaires, performance reviews, security ratings, and audits—not just at onboarding.

  24. What is a vendor questionnaire used for?

    A structured set of questions sent to a third party to gather information about its security controls, policies, certifications, and risk posture as part of assessment and ongoing monitoring.

  25. What is the difference between internal and external compliance reporting?

    Internal reporting communicates compliance status to management/board within the organization to support decisions. External reporting provides compliance information to regulators, auditors, partners, or the public to demonstrate adherence.

  26. List common consequences of non-compliance.

    Fines, sanctions, reputational damage, loss of license, contractual impacts (loss of business/contracts), and potential legal/criminal liability.

  27. What is continuous compliance monitoring, and why is it preferred over point-in-time checks?

    Ongoing, often automated, verification that controls and configurations remain compliant. It is preferred because it detects drift and violations in near real time, rather than only at scheduled audit intervals.

  28. What is attestation in the context of compliance?

    A formal declaration or acknowledgment—often signed by management or a third party—affirming that controls are in place and the organization meets specific compliance requirements.

  29. What are common legal implications/scopes of compliance: local, national, and global?

    Compliance obligations vary by jurisdiction—local (city/state), national (country-wide laws), and global/international (cross-border regulations like GDPR)—and organizations must satisfy all applicable layers where they operate.

  30. What is the difference between data inventory and data retention in a privacy program?

    Data inventory catalogs what personal/sensitive data is held, where it lives, and how it flows. Data retention defines how long data is kept and when it must be securely disposed of, per policy and law.

  31. What is the 'right to be forgotten'?

    A privacy right (notably under GDPR) allowing individuals to request that an organization delete their personal data when there is no compelling reason to keep it.

  32. Differentiate the roles of data subject, data owner, and data controller in privacy.

    Data subject = the individual whom the personal data is about. Data owner = internal party accountable for the data's classification/protection. Data controller = the entity that decides the purposes and means of processing the data.

  33. What is the difference between an internal audit and an external audit?

    An internal audit is performed by the organization's own staff to evaluate controls and readiness. An external audit is conducted by an independent third party, providing impartial verification and credibility (e.g., regulatory or certification audits).

  34. What is the difference between an audit, an assessment, and a penetration test?

    An audit verifies compliance against a defined standard/control set. An assessment broadly evaluates security posture and gaps. A penetration test actively exploits vulnerabilities to demonstrate real-world impact.

  35. What is attestation versus examination in independent assessments?

    In an attestation engagement, an auditor reports on management's own assertion about controls. In an examination, the auditor independently tests and forms an opinion on the controls/subject matter directly.

  36. What is phishing, and how does it differ from spear phishing and whaling?

    Phishing = mass fraudulent messages to trick users into revealing data or clicking malicious links. Spear phishing = targeted at a specific individual/group. Whaling = spear phishing aimed at high-value executives (the 'big fish').

  37. Differentiate phishing, vishing, smishing, and pharming.

    Phishing = fraudulent email. Vishing = voice/phone-based. Smishing = SMS/text-based. Pharming = redirecting users to a fake site (e.g., via DNS poisoning) without requiring them to click a link.

  38. What are common indicators that help users recognize a phishing message?

    Urgent or threatening language, requests for credentials/payment, generic greetings, mismatched or spoofed sender addresses, suspicious links/attachments, spelling/grammar errors, and unexpected requests that bypass normal process.

  39. What is anomalous behavior recognition in user security awareness?

    Training users and systems to detect deviations from normal patterns—risky behavior, unexpected actions, or unintentional behavior—that may indicate compromise or insider threat.

  40. Classify the three types of anomalous behavior emphasized in Security+ user guidance.

    Risky behavior (knowingly dangerous actions), unexpected behavior (out-of-pattern activity), and unintentional behavior (accidental mistakes such as misdirected email or accidental data exposure).

  41. What topics should comprehensive user guidance and security awareness training cover?

    Policies/handbooks, situational awareness, insider threat, password management, removable media/cables, social engineering, operational security, and hybrid/remote work practices.

  42. What is operational security (OPSEC) guidance for users?

    Teaching users to protect sensitive information by limiting what details (about systems, projects, or routines) they disclose, since seemingly harmless data can be aggregated by adversaries for attacks.

  43. What is an insider threat, and what user guidance reduces it?

    A security risk originating from people inside the organization (employees, contractors). Guidance includes least-privilege access, monitoring, reporting suspicious behavior, and clear acceptable-use and data-handling policies.

  44. What are the key phases of developing and executing a security awareness program?

    Develop (design content and objectives), Execute (deliver training/campaigns), Review/measure (assess effectiveness via metrics like phishing click rates), and continuously improve based on results.

  45. Why is a security awareness program treated as a recurring cycle rather than a one-time event?

    Because threats evolve, staff change, and behavior reverts over time; continuous reinforcement, periodic phishing simulations, and metric-driven updates keep users effective against current attacks.

  46. What metrics measure the effectiveness of a phishing awareness/anti-phishing campaign?

    Phishing simulation click-through rates, reporting rates (how many users report the test), time-to-report, repeat-offender counts, and trends in these metrics over successive campaigns.

  47. What is the purpose of recognizing and reporting phishing attempts (the 'report' behavior)?

    Prompt reporting lets security teams contain threats, warn other users, block malicious senders/links, and improve defenses—turning each user into an active sensor in the human firewall.

  48. What is a gap analysis in the context of audits and assessments?

    A comparison of an organization's current security state against a desired standard or framework to identify the differences ('gaps') that must be remediated to reach compliance.

  49. What is the difference between compliance monitoring done internally versus by an external entity?

    Internal compliance monitoring uses the organization's own tools/staff for self-assessment and continuous oversight. External monitoring involves regulators or third-party auditors verifying adherence, often required for certifications or legal obligations.

  50. What is supply chain risk, and why is vendor monitoring critical to it?

    Supply chain risk is the threat that a compromised vendor, supplier, or service provider introduces vulnerabilities into your environment. Ongoing vendor monitoring is critical because a third party's security posture can degrade after onboarding.

  51. What is the difference between an SLA and an OLA?

    An SLA (Service Level Agreement) is between a service provider and an external customer. An OLA (Operational Level Agreement) defines responsibilities between internal teams/departments that support delivery of that SLA.

CompTIA Security+ Security Program Management and Oversight FAQ

What is in the CompTIA Security+ Security Program Management and Oversight syllabus?

CompTIA Security+ Security Program Management and Oversight is split into 5 chapters: Security Governance, Risk Management, Third-Party Risk Management, Security Compliance and Audits and Security Awareness. Together they contain 23 topics and 45 sub-topics.

How many chapters are in CompTIA Security+ Security Program Management and Oversight?

5 chapters, containing 23 topics and 45 sub-topics. The largest chapter is Security Governance, with 5 topics.

Are there flashcards for CompTIA Security+ Security Program Management and Oversight?

Yes — a 71-card Security Program Management and Oversight deck, printed in full in the flashcards section of this page and available in the Examius app with spaced repetition. The free plan covers one exam of your choice, including its flashcards; Examius Pro, a one-time purchase, unlocks every other exam and deck.