The official CompTIA Security+ syllabus, organized by domain. Check off each point as you review it.
Inicia sesión para guardar tu progreso entre sesiones.
1.1 Explain security concepts and controls.
Defense in depth layers people, technology and operations barriers so that what one layer misses another catches. The CIA triad protects confidentiality, integrity and availability; AAA separates authentication, authorization and accounting (records of what was done). Non-repudiation prevents denying an action, least privilege limits rights and Zero Trust decides each access without implicit trust.
NIST CSRC Glossary: defense-in-depth ↗RFC 2989: Criteria for Evaluating AAA Protocols for Network Access ↗
Control categories describe who or what applies a control. Technical controls are executed by hardware, software or firmware mechanisms (firewalls, account lockout); managerial controls focus on managing risk and the security program (risk assessments, policies); operational controls are executed by people (training, help desk procedures) and physical controls protect facilities and equipment.
NIST CSRC Glossary: technical controls ↗NIST CSRC Glossary: operational controls ↗
Control types describe when and how a control acts: preventive stops the incident (USB blocking, IPS), deterrent discourages the attacker (warning signs), detective finds what happened (IDS, log review), corrective restores the situation (restoring backups), directive tells people what to do (policies) and compensating gives comparable protection when the normal control cannot be applied.
NIST CSRC Glossary: compensating controls ↗NIST CSRC Glossary: security ↗
1.2 Given a scenario, demonstrate the impact of change management processes on security.
A change is requested, recorded, analyzed for security impact, tested and approved by the change advisory board (CAB), which receives the test plan and results. The request names an owner, the stakeholders to notify, a maintenance window and a backout plan. Detected changes are reconciled by checking for an approved request and whether they occurred in the scheduled window.
NIST SP 800-128: Guide for Security-Focused Configuration Management of Information Systems ↗
A change has technical consequences to plan for: new software must be added to the allow list under deny-all, permit-by-exception; dependencies on other systems are part of impact analysis; legacy applications may fail under hardened configurations; and the implementer is limited to approved activities, with notice given when restarts or downtime will occur.
NIST SP 800-128: Guide for Security-Focused Configuration Management of Information Systems ↗NIST SP 800-53 Rev. 5: Security and Privacy Controls ↗
A change is not finished when it is deployed: network diagrams, technical designs, the baseline configuration, inventory, security plan and the procedures used by the help desk and users must be updated. This applies to pre-approved standard changes too. The previous baseline and approval records are kept unchanged for traceability, audits and possible rollback.
NIST SP 800-128: Guide for Security-Focused Configuration Management of Information Systems ↗
Version control keeps code, configuration as code and baseline configurations in a repository that records every change and the account that made it. Keeping previous versions makes it possible to return to an approved configuration and helps audits and incident response. Because history keeps everything, a committed secret stays exposed even if deleted later: it must be revoked and rotated.
NIST SP 800-218: Secure Software Development Framework (SSDF) ↗OWASP Secrets Management Cheat Sheet ↗
1.3 Explain the importance of using appropriate cryptographic solutions.
In a PKI each identity has a key pair: the public key can be shared and is used to encrypt data for the owner and verify the owner's signatures; the private key is never published and is used to sign and decrypt. Key escrow retains the private key tied to an encryption certificate so data can be recovered if the user loses it or leaves the organization.
NIST CSRC Glossary: private key ↗NIST CSRC Glossary: key escrow ↗
A certificate authority issues and revokes certificates, and its root is the starting point of trust. A CRL is a signed, periodic list of revoked certificates, while OCSP checks one certificate's status with more timely information. A CSR carries the public key signed with the private key. A self-signed certificate depends on secure distribution, and a wildcard covers one left-most label only.
RFC 6960: Online Certificate Status Protocol - OCSP ↗RFC 9525: Service Identity in TLS ↗
Symmetric encryption (AES) uses the same key to encrypt and decrypt and handles large volumes; asymmetric encryption (RSA, ECC) establishes keys and signs in hybrid schemes. Disk, partition or volume encryption protects against theft of a powered-off device but not on a running system; database or record encryption protects specific values. TLS 1.3 allows only key exchanges with forward secrecy.
OWASP Cryptographic Storage Cheat Sheet ↗RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3 ↗
A digital signature is generated with the signer's private key and verified with the public key; it proves origin and data integrity and provides non-repudiation because only the signer holds the private key. An HMAC uses a shared key and gives no non-repudiation. Code signing with certificates from an established CA lets operating systems check who published an executable and whether it was altered.
NIST CSRC Glossary: digital signature ↗NIST SP 800-218: Secure Software Development Framework (SSDF) ↗
A salt is a unique random value combined with each password before hashing it with a slow password hashing scheme. It makes identical passwords produce different hashes and defeats precomputed rainbow tables. It is stored with the hash and need not be secret; the secret value kept elsewhere is a pepper. Slowness comes from the cost factor, not the salt.
OWASP Password Storage Cheat Sheet ↗NIST SP 800-63B-4: Authentication and Authenticator Management ↗
Cryptographic tools protect keys at different points. A TPM is a motherboard chip that generates keys and stores small secrets for its own device, such as the disk encryption key. An HSM is a dedicated, tamper-resistant device that safeguards keys and performs cryptographic operations, for example for a CA. A KMS automates the whole key lifecycle, and a secure enclave isolates data within the processor.
NIST CSRC Glossary: trusted platform module ↗NIST CSRC Glossary: hardware security module (HSM) ↗
Obfuscation hides or replaces data so it cannot be read or seen. Steganography hides the existence of a message inside another file, such as an image. Masking removes or replaces a value, for example with asterisks, without preserving its analytic utility. Pseudonymization swaps identifiers for pseudonyms and lets a person's records be linked without revealing who they are.
NIST CSRC Glossary: steganography ↗NIST CSRC Glossary: pseudonymization ↗
A hash function produces a fixed-length digest; it is one-way and collision-resistant, so it verifies that a file or message has not changed but cannot recover data, which requires encryption. Per NIST, the SHA-2 family (for example SHA-256) is acceptable for all uses, while SHA-1 is disallowed for generating digital signatures; MD5 is not part of the Secure Hash Standard.
FIPS 180-4: Secure Hash Standard (SHS) ↗NIST SP 800-131A Rev. 2: Transitioning the Use of Cryptographic Algorithms and Key Lengths ↗