Study guide
4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI
CISSP Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CISSP Orientation, CAT, and Official Source Control
1.1 Credential Scope, CISSP Mindset, and Search Language 1.2 Exam Outline Effective Date and Eight-Domain Map 1.3 CAT Format, 100-150 Items, and Forward-Only Rules 1.4 Passing Grade, Results, Feedback, and Retake Policy 1.5 Experience, Endorsement, and Associate of ISC2 Path 1.6 Pricing, AMF, CPE, and Maintenance Overview
2 Chapter 2: Security and Risk Management
2.1 Professional Ethics, CIA, and Security Governance 2.2 Policies, Standards, Procedures, Guidelines, and Control Ownership 2.3 Legal, Regulatory, Privacy, and Investigation Context 2.4 Risk Identification, Analysis, Treatment, and Reporting 2.5 Business Continuity, BIA, and Recovery Prioritization 2.6 Personnel Security, Training, Awareness, and Culture 2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance 2.8 Security and Risk Management Case Lab
3 Chapter 3: Asset Security and Data Lifecycle
3.1 Asset and Data Classification, Ownership, and Roles 3.2 Handling Requirements, Labeling, Privacy, and Cross-Border Data 3.3 Data States and Protection Methods: DLP, DRM, and CASB 3.4 Data Lifecycle, Retention, Remanence, and Destruction 3.5 Secure Provisioning, Inventory, and Asset Management 3.6 Asset Security Case Lab
4 Chapter 4: Security Architecture, Engineering, and Cryptography
4.1 Secure Design Principles and Security Models 4.2 Control Selection, System Security, and Architecture Risk 4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI 4.4 Cryptographic Lifecycle, Key Management, and Attack Patterns 4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture 4.6 Physical Site, Facility, and Environmental Security 4.7 Information System Lifecycle Engineering and Retirement 4.8 Architecture and Engineering Case Lab
5 Chapter 5: Communication, Network Security, and Zero Trust
5.1 Network Architecture, OSI/TCP/IP, and Secure Design 5.2 Secure Protocols, Encryption in Transit, and Channel Protection 5.3 Segmentation, Microsegmentation, SDN, VPC, and Zero Trust 5.4 Wireless, Cellular, Remote Access, and Third-Party Connectivity 5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints 5.6 Monitoring, Observability, Capacity, and Resilient Communications 5.7 Communication and Network Security Case Lab
6 Chapter 6: Identity and Access Management
6.1 Identity Proofing, Authentication, Authorization, and Accountability 6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access 6.3 Federation, SSO, MFA, Passwordless, and Session Management 6.4 Provisioning, Deprovisioning, JML, and Access Reviews 6.5 Service Accounts, Non-Human Identities, and Privilege Management 6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries 6.7 IAM Case Lab
7 Chapter 7: Security Assessment, Testing, and Audit Strategy
7.1 Assessment, Test, and Audit Strategy Selection 7.2 Control Testing, Vulnerability Assessment, and Penetration Testing 7.3 Log Review, Code Review, Misuse Cases, and Compliance Checks 7.4 Security Process Data, KPIs, KRIs, and Reporting 7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality 7.6 Security Assessment and Testing Case Lab
8 Chapter 8: Security Operations, Incident Response, and Resilience
8.1 Investigations, Evidence, Forensics, and Legal Readiness 8.2 Logging, Monitoring, SOC, and Alert Triage 8.3 Configuration, Change, Patch, and Vulnerability Operations 8.4 Incident Management, Containment, Eradication, and Recovery 8.5 Disaster Recovery, Backup, Availability, and Resilience 8.6 Physical Security Operations and Safety 8.7 Security Operations Case Lab
9 Chapter 9: Software Development Security and DevSecOps
9.1 Secure SDLC Governance and Requirements 9.2 Architecture, Threat Modeling, and Design Review 9.3 Secure Coding, Code Review, and Application Testing 9.4 CI/CD, Source Control, and Environment Separation 9.5 Software Supply Chain, Third-Party Components, and Deployment 9.6 DevSecOps Vulnerability Management and Release Risk 9.7 Software Development Security Case Lab
10 Chapter 10: Integrated CISSP Governance Scenario Labs
10.1 Enterprise Risk Committee Decision Lab 10.2 Cloud Migration Security Architecture Lab 10.3 Ransomware Incident and Business Continuity Lab 10.4 Identity Modernization and Zero Trust Lab 10.5 Third-Party Breach and Contract Governance Lab 10.6 Secure SDLC Transformation Lab 10.7 Full CISSP Manager Simulation
11 Chapter 11: Final Review, Endorsement, CPE, and Test-Day Strategy
11.1 Final 45-Day CISSP Study Plan 11.2 CAT Timing and Forward-Only Decision Workflow 11.3 Mixed-Domain Remediation and Manager Mindset Review 11.4 Test-Day Checklist and Pearson VUE Readiness 11.5 Endorsement, Associate Path, and Work Experience Documentation 11.6 CPE, AMF, and Three-Year Maintenance Plan 11.7 CISSP Final Mixed Review
4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI
Key Takeaways Explain This Topic AI
Cryptography should be selected to meet confidentiality, integrity, authentication, and nonrepudiation objectives, not to show mathematical sophistication.
Symmetric encryption is efficient for bulk data, while asymmetric cryptography helps with key exchange, identity, digital signatures, and trust establishment.
Hashing provides integrity evidence, and message authentication codes add shared-secret authenticity.
PKI depends on certificate lifecycle management, trust anchors, revocation, validation, and clear ownership.
Last updated: May 2026
Practical Cryptography for Security Leaders
Cryptography supports confidentiality, integrity, authentication, and nonrepudiation, but it does not solve every security problem. It cannot fix weak authorization, poor endpoint hygiene, excessive data collection, exposed secrets, or a broken business process. The CISSP mindset is to select cryptographic services that fit risk, implementation maturity, and operational reality.
Symmetric encryption uses the same secret key to encrypt and decrypt. It is fast and well suited for bulk data such as files, databases, backups, and network sessions after a session key has been established. The main challenge is not speed; it is distributing, storing, rotating, and protecting shared keys at scale.
Asymmetric cryptography uses a public key and private key pair. What one key does, the related key is needed to reverse or verify, depending on the scheme. It is slower than symmetric encryption, so it is commonly used for key exchange, digital signatures, certificate validation, and identity establishment rather than encrypting large datasets directly.
Hybrid designs are common. TLS, for example, uses asymmetric mechanisms and certificates to authenticate parties and agree on session secrets, then uses symmetric encryption for efficient protected communication. This pattern reflects a practical balance: use asymmetric cryptography for trust establishment and symmetric cryptography for high-volume protection.
Hash functions produce a fixed-length digest from input data. A good cryptographic hash is one way, collision resistant for practical purposes, and sensitive to changes in the input. Hashes help verify integrity for files, software artifacts, logs, and evidence, but a plain hash does not prove who created the data because anyone can compute it.
Message authentication codes add shared-secret authenticity to integrity. An HMAC can show that a party with the shared secret created or validated a message. Digital signatures provide a different property: a private key signs, and others can verify using the public key. That supports stronger accountability when the private key is controlled by a specific person, service, or organization.
- Need Common mechanism Managerial concern
- Protect stored data Symmetric encryption Key custody, backup access, rotation
- Establish secure sessions Hybrid protocol such as TLS Certificate validation, protocol settings
- Verify file integrity Cryptographic hash Trusted source for expected digest
- Authenticate messages HMAC or digital signature Secret sharing or private key control
- Support nonrepudiation Digital signature with governance Identity proofing, key protection, audit trail
Public key infrastructure provides a trust framework for certificates. A certificate binds a public key to an identity or purpose, and a certificate authority signs that binding. Relying parties decide whether to trust the certificate by validating the chain to a trusted root, checking names and usage constraints, and considering revocation status.
PKI is operationally demanding. Certificate requests, issuance, approval, installation, renewal, revocation, monitoring, and retirement must be owned. Expired certificates can create outages, weak validation can enable impersonation, and uncontrolled certificate issuance can create shadow trust relationships that bypass security governance.
Root certificate authorities require the highest protection because they anchor trust. Many organizations keep roots offline and use intermediate authorities for daily issuance. This reduces exposure and allows a compromised intermediate to be revoked without replacing every trust anchor. The design should define who can issue certificates, for what names, under which policy, and with what audit evidence.
Certificate revocation is a practical risk area. Certificate revocation lists and online certificate status protocols both have availability and freshness tradeoffs. Some environments use short-lived certificates to reduce reliance on revocation checking. The right answer depends on impact, connectivity, automation maturity, and tolerance for service disruption.
Cryptographic choices should follow recognized standards and approved libraries. Custom algorithms, homegrown random number generators, and unusual protocol combinations are warning signs. A security leader does not need to derive the math, but must know enough to challenge nonstandard choices and require review by qualified cryptographic engineers.
Key size and algorithm strength matter, but so do mode, padding, initialization, randomness, and implementation. Strong encryption can fail if the same nonce is reused where uniqueness is required, if private keys are stored in source code, or if applications accept invalid certificates. Operational misuse is often more likely than a theoretical break.
Data state matters. Data at rest may require database, file, disk, object storage, or backup encryption. Data in transit usually requires secure protocols and certificate validation. Data in use may require memory protections, trusted execution environments, tokenization, or process controls, but encryption alone cannot fully protect data while it is actively processed.
Use this selection checklist before approving cryptography in a design:
Define the security objective: confidentiality, integrity, authentication, nonrepudiation, or a combination.
Use standard algorithms, protocols, libraries, and platform services.
Identify key owners, custodians, storage locations, and recovery procedures.
Confirm certificate validation, hostname checks, and revocation or short-lived certificate strategy.
Document where plaintext exists and who can access it.
Test failure cases such as expired certificates, revoked keys, and unavailable key services.
For study purposes, stay practical. Know the difference between encryption, hashing, HMACs, digital signatures, and certificates. More importantly, know when each is appropriate and what governance is needed to keep the cryptographic control from becoming a fragile dependency.