CCNA Casp Engineering Crypto Questions

Just-in-time access issues credentials only for a bounded period, so stolen or misused sessions expire quickly. This shrinks the window attackers have to pivot between systems, directly delivering the reduced lateral-movement risk the stem asks for.

Digitally signing firmware with a private key lets devices verify the signature using the corresponding public key before installation, so any tampered or forged image fails validation. This cryptographically ensures only vendor-authorised firmware is accepted.

ChaCha20-Poly1305 relies solely on ARX operations, which execute efficiently in software on CPUs lacking AES-NI hardware acceleration. AES-256-GCM depends on dedicated AES instructions for competitive throughput, so on such constrained devices ChaCha20-Poly1305 delivers markedly faster encryption, directly satisfying the stem's "certain environments" constraint.

AES-256-GCM combines AES counter-mode encryption with GHASH authentication, producing ciphertext and a tag in one operation. This satisfies the stem's single-pass requirement, unlike separate encrypt-then-MAC schemes. It also delivers the confidentiality and integrity the organization demands, using a 256-bit key for strong protection.

SPIFFE/SPIRE issues short-lived, cryptographically verifiable identities (SVIDs) to workloads based on attested node and pod attributes, and automatically rotates them. mTLS using these SVIDs lets each service authenticate peers without embedded static secrets, satisfying the rotation requirement when pods move.

Tamper-responsive mechanisms detect physical intrusion attempts (e.g., drilling, voltage tampering) and automatically erase sensitive key material. This prevents attackers from extracting keys even if they gain physical access to the HSM. It is a critical security property for HSMs used in CAs, as it ensures that keys cannot be recovered from a compromised device.

Per-archive data keys limit the blast radius of any single key exposure, and wrapping them under a root key that never leaves the HSM means the wrapped copies stored alongside the archives are useless without it. Deleting the root key destroys the only means of unwrapping, so every archive becomes permanently unrecoverable even if the bucket is fully copied, satisfying crypto-shredding.

Intel SGX uses the CPU's memory encryption engine to encrypt enclave pages when they are written to DRAM and verify their integrity when read back. This ensures that even a privileged attacker like the OS or hypervisor cannot read or modify enclave memory. The encryption keys are managed by the CPU and never exposed to software.

EAP-TLS provides mutual authentication using digital certificates for both the client and the server, and it integrates with a RADIUS server for centralized policy enforcement. This meets the requirements for WPA3-Enterprise, which mandates 802.1X authentication and supports EAP-TLS as a secure method.

An offline root CA issues only to subordinate issuing CAs, each scoped to one purpose, so compromising a user-issuing CA cannot forge code-signing or device certificates. This satisfies the constraint of minimising compromise blast radius through cryptographic and operational separation.

SHA3-256 uses the Keccak sponge construction rather than Merkle-Damgard, so it is inherently resistant to length-extension attacks. It is FIPS 202 approved and acceptable under FIPS 140-3 validated modules, and it provides 128-bit collision resistance, which is sufficient for a 15-year firmware-signing lifespan. It therefore satisfies every stated requirement without additional mitigations.

Dual control requires two or more individuals to authorize an action, and split knowledge ensures that no single person possesses the entire key or the means to use it. Together, they enforce separation of duties, preventing a lone administrator from generating and using a key without oversight. This is a fundamental principle in high-security key management, such as in FIPS 140-2 Level 3 or higher validated modules.

TLS_AES_256_GCM_SHA384 is a TLS 1.3 cipher suite that uses AES-256 in GCM mode for encryption and SHA-384 for the hash. In TLS 1.3, all cipher suites provide forward secrecy by default because key exchange uses ephemeral Diffie-Hellman. This suite is strong and meets the requirements for PFS and strong encryption.

AllowUsers explicitly defines which user accounts may authenticate via SSH. When password authentication is disabled and root login is prohibited, this directive further narrows access to only the named administrative accounts. It directly addresses the requirement to restrict access to authorized users and is a standard hardening step for SSH daemons on public-facing servers.

This sequence appends an ACCEPT rule for the internal subnet, then appends a DROP rule for all other traffic. Because iptables processes rules in order, packets from 10.0.0.0/24 match the first rule and are accepted; all other packets fall through to the DROP rule. This correctly implements the requirement.

An HSM provides dedicated tamper-resistant hardware that generates, stores and uses cryptographic keys internally, so keys never leave the device in plaintext. FIPS 140-2 Level 3 certification confirms physical tamper resistance, satisfying the requirement for secure signing in hardware.

The Strict-Transport-Security header instructs browsers to upgrade all future requests for the domain to HTTPS for the specified max-age, and includeSubDomains extends this to subdomains while preload allows inclusion in browser preload lists. This directly prevents protocol downgrade and plaintext requests after the first secure visit.

A policy engine that consumes identity and device-posture signals and enforces decisions through a policy enforcement point on every request is the core of zero trust. It removes implicit trust based on network location and makes access contingent on current device health and authenticated identity, matching the stated requirement precisely.

Microsegmentation enforces least privilege between workloads, so a compromised workstation cannot freely reach other systems. Combined with default-deny rules, it contains an intruder and is a core mechanism for limiting lateral movement in a zero trust design.

ECDSA P-384 provides a 192-bit security strength, exceeding RSA-2048 and matching the strongest IKEv2 authentication options. It satisfies the stem's demand for maximum security by using elliptic-curve cryptography, which delivers equivalent strength with smaller keys and is approved for CNSA suite compliance.

Automatic revocation after use or expiry is fundamental to JIT: standing privileges are eliminated, so access exists only for the approved window. Once the task completes or the timer lapses, the entitlement is withdrawn without manual intervention, shrinking the attack surface.

A default-deny seccomp profile removes access to the large majority of system calls a process never needs, shrinking the kernel interfaces an attacker can abuse from inside a compromised container. Because it is enforced per process by the kernel, a successful application exploit cannot pivot to unneeded calls such as those used to load modules or manipulate namespaces, directly reducing escape options.

Diffie-Hellman group exchange with SHA-1 uses a deprecated hash for key exchange integrity, weakening SSH against collision-based attacks. Disabling it enforces stronger SHA-2-based key exchange algorithms, meeting the requirement to restrict the jump host to the most secure options.

Network policies can select pods and control egress by destination CIDR and port, so a rule denying 169.254.169.254 blocks the metadata path while a companion allow rule permits required external APIs. This is the least-disruptive control that directly removes the credential-theft vector without breaking legitimate traffic. It enforces the restriction at the pod network layer regardless of application behavior.

Many HSMs support cloning or secure backup where the key is transferred between devices in a wrapped, hardware-protected form and never exists as a recoverable plaintext blob. Storing the backup on a second, geographically separate HSM preserves availability after device failure while keeping the private key inside certified hardware boundaries, satisfying both the no-plaintext and restoration requirements.

SAST analyzes source code for vulnerabilities without executing it, enabling early detection of issues like SQL injection or buffer overflows. Integrating SAST into the CI/CD pipeline ensures continuous security checks. This helps developers fix flaws before deployment, reducing risk.

XMSS is a stateful hash-based signature scheme whose security rests solely on hash-function collision resistance, so it resists quantum attacks via Shor's algorithm. It satisfies the quantum-resistance requirement while signing and verifying quickly, meeting the high-performance constraint. Its stateful nature, however, demands careful key-state management to prevent reuse of a one-time key.

SELinux in enforcing mode applies mandatory access control, restricting processes to only the resources defined in the policy. A targeted policy confines specific services like the web server, limiting the impact of a compromise. This meets the requirement to confine the web server process even if exploited.

TLS 1.3 mandates ephemeral Diffie-Hellman key exchange for all cipher suites, so every session derives unique keys and compromise of the long-term key cannot decrypt past traffic. Earlier versions permitted static RSA key transport, which lacked this property.

Certificate Transparency logs are append-only, publicly auditable records of issued certificates. Monitoring them reveals certificates issued for a domain without authorisation, so a compromised issuing CA's rogue certificates become detectable, satisfying the requirement to detect unauthorised issuance.

Default-deny network policies stop unauthorized cross-namespace connections, while scoping secret mounts and service account permissions to only the pods that need them prevents a compromised pod from reading other tenants' secrets. Together they address both the network and secret-access requirements directly.

An offline root CA, with its private key held in a hardware security module, is unreachable from the network, so compromise of issuing or web servers cannot expose it. This directly minimises the risk the security team wants to avoid.

An offline root CA keeps the trust anchor's private key on an isolated system that is powered on only to sign the subordinate CA certificate. The online issuing subordinate CA handles routine end-entity issuance, so compromise of the issuing CA does not expose the root key, and the root cannot be used remotely. This directly satisfies both the isolation and low-volume issuance requirements.

A hypervisor-based firewall enforces security policies at the virtual switch level, controlling traffic between VMs even on the same host. This is critical for microsegmentation because it prevents lateral movement within the virtualized environment. It ensures that a compromised web server VM cannot communicate with database VMs unless explicitly allowed, directly supporting the goal.

Just-in-time access provisioning grants elevated permissions only for the duration of a specific task, then automatically revokes them. This directly eliminates standing privileges, satisfying the stem's requirement that access be temporary and self-expiring. Microsoft Entra ID Privileged Identity Management implements this through time-bound role activation, with approvals and expiry enforced automatically.

Proper VLAN tagging and avoiding native VLANs on trunk ports prevent VLAN hopping attacks, where an attacker could send double-tagged frames to access another VLAN. This ensures that the segmentation at Layer 2 is robust and that traffic cannot inadvertently cross VLAN boundaries.

Fail2ban monitors log files for failed authentication attempts and dynamically updates firewall rules to block offending IP addresses. It can be configured to limit failed SSH attempts and ban IPs for a specified duration. This directly meets the requirement of protecting against brute-force attacks by blocking sources after multiple failures.

Certificate Transparency publishes every issued certificate to append-only, cryptographically verifiable logs, letting the team detect unauthorised or forged certificates for their domains. Monitoring these logs satisfies the misissuance detection requirement by exposing certificates the legitimate CA never intended to issue.

PCRs hold cumulative hash measurements of each boot component, extending values sequentially so any tampering alters the final register state. This satisfies the measured boot requirement, letting attestation compare PCR values against known-good baselines to detect modification before execution.

FIDO2/WebAuthn security keys satisfy both constraints: cryptographic challenge–response using per-origin public/private key pairs, so no shared secret traverses the wire, and origin binding prevents credential replay on lookalike phishing domains. Microsoft Entra ID supports these keys as phishing-resistant authentication, unlike OTP or push methods.

Keeping the root CA offline means its private key is never exposed on a network-connected host, so compromise of subordinate systems cannot forge the trust anchor. It is brought online only for cross-certification or disaster recovery, preserving hierarchy integrity and manageability.

The policy administrator is responsible for executing the decisions made by the policy engine. It configures the data plane to allow or deny connections, often by instructing gateways or agents. It is essential for enforcing least privilege because it dynamically provisions access based on the policy engine's verdict. Together with the policy engine, it forms the control plane.

FIDO2/WebAuthn binds the credential's private key to the relying party's origin, so a phishing site on a different domain cannot invoke it. This origin-scoped cryptographic assertion removes the shared-secret replay weakness inherent in password-based authentication.

Envelope encryption with a unique data encryption key per tenant ensures that compromising one tenant's key reveals only that tenant's data. The key encryption key wraps each data key, so destroying a single wrapped data key renders that tenant's ciphertext permanently unrecoverable, achieving cryptographic erasure without touching other tenants or re-encrypting the database. This satisfies isolation, erasure, and operational efficiency requirements.

Tunnel mode encapsulates the complete original IP packet, header included, inside a new IP packet, so the original addresses are hidden. ESP provides confidentiality and integrity for that payload. Transport mode would leave the original header exposed, failing the stated requirement.

Code signing binds the firmware to a trusted publisher's private key, so devices can verify authenticity and integrity before flashing. This directly satisfies the OTA constraint: preventing attackers from pushing tampered or malicious firmware images to fielded devices.

A service mesh with mTLS provides encryption and mutual authentication for service-to-service communication. It uses sidecar proxies to manage certificates and identity without relying on static IPs, which suits containerized environments. This directly meets the requirements for encrypted, mutually authenticated traffic in a dynamic infrastructure.

ESP encrypts the payload and authenticates its origin and integrity, delivering confidentiality plus authentication in one protocol. Tunnel mode encapsulates the entire original packet, so the site-to-site VPN's demand for both services is met without adding AH alongside.

Constant-time cryptographic operations eliminate the data-dependent execution timing that leaks ECDSA nonce and scalar information, directly satisfying the stem's timing side-channel constraint. By ensuring every operation takes identical duration regardless of secret values, the attacker gains no exploitable timing variance to correlate against the private key.

Session recording and monitoring create an auditable trail of every privileged action on critical servers, satisfying the PAM requirement for accountability and detecting misuse or insider threats in real time. This directly supports the scenario's goal of enhancing security for privileged access to critical infrastructure.

This rule triggers an alert when the string '1=1' is found in TCP traffic destined for port 80. The content option performs a simple pattern match, which is effective for detecting known SQL injection strings. The alert action logs the event, allowing the administrator to be notified of potential attacks.

SELinux in enforcing mode applies mandatory access controls that confine the web server process to only the resources defined in its policy. This limits the impact of a compromise by preventing the process from accessing files or network ports outside its defined domain, thus achieving least privilege and confinement.

RadSec encapsulates RADIUS in TLS, providing encryption and integrity for the shared secret and all authentication traffic. Standard RADIUS uses a shared secret to obfuscate passwords but does not encrypt the entire packet, leaving it vulnerable to eavesdropping. RadSec protects against this by securing the entire communication channel.

A service mesh such as Istio or Linkerd provides transparent mTLS for all inter-service communication, encrypting traffic and authenticating both ends using service identities (e.g., SPIFFE IDs). It also enables fine-grained authorization policies based on those identities. This directly satisfies the requirements for encryption, mutual authentication, and identity-based authorization.

Lattice-based key exchange mechanisms like Kyber are designed to be resistant to quantum attacks while also supporting ephemeral key generation to provide perfect forward secrecy. Kyber is a NIST-standardized post-quantum algorithm, making it the best choice for this scenario that demands both PFS and quantum resistance.

PCRs are shielded registers that hold cumulative hashes of firmware and software measurements taken during boot. Secure boot compares these values against expected ones, and attestation reports them, so PCRs provide the measurement storage underpinning both features.

FIDO2/WebAuthn satisfies both constraints by using public-key cryptography: the authenticator holds a private key, while the server stores only the public key, so no shared secret crosses the wire. Origin binding ties each credential to the legitimate domain, defeating phishing proxies that replay credentials against lookalike sites.

Policy decisions only matter if they are enforced inline. Identity-aware proxies act as policy enforcement points that terminate sessions and apply the decision point's verdict per request, which is how continuous verification becomes effective. They also hide application endpoints so that access cannot bypass the control path, supporting the zero trust principle of never trusting the network.

ChaCha20-Poly1305 is a stream cipher with AEAD that runs efficiently in software without AES hardware acceleration, suiting constrained IoT processors. Its low memory footprint and fast performance deliver confidentiality and integrity with minimal overhead in harsh environments.

S/MIME certificates bind an individual's verified identity to a public key, enabling message signing and encryption within mail clients. This validates the sender's identity for email, precisely matching the stated requirement for individual identity validation.

Enabling kernel module signing enforcement ensures that the kernel will only load modules that are signed with a trusted key. This prevents unsigned or malicious modules from being loaded, even by root, thus blocking rootkits that rely on kernel modules. This directly satisfies the requirement to allow only signed and trusted kernel modules.

WPA3-Personal with SAE (Simultaneous Authentication of Equals) is the strongest available method for a pre-shared key network. SAE replaces the WPA2 four-way handshake with a Dragonfly handshake that provides forward secrecy and protects against offline dictionary attacks. It does not require an authentication server and is supported by modern devices. This meets all requirements: strongest encryption/authentication and no separate server.

Taking the root CA offline and physically securing it prevents network-based compromise and unauthorised access to the trust anchor. This satisfies the three-tier hierarchy requirement by isolating the root from the issuing CA and registration authority, so its private key is only used for signing subordinate CAs.

The boot ROM's stored public key forms an immutable root of trust, so the bootloader verifies the kernel's digital signature before transferring control. This chains trust from ROM to kernel, enforcing the requirement that only signed code executes on the embedded device.

FIDO2/WebAuthn binds credentials to the origin via public-key cryptography, so a phishing site on a lookalike domain cannot replay the assertion. Hardware authenticators such as security keys store the private key in tamper-resistant silicon, never exposing it. This satisfies the stem's twin constraints: hardware-based cryptographic authentication and phishing resistance.

A file integrity monitoring agent using SHA-256 provides a strong cryptographic baseline, and storing it in a remote, append-only repository prevents a local root attacker from silently rewriting the reference data. Automated comparison against that trusted baseline detects unauthorized changes and generates alerts. This combination satisfies the cryptographic, tamper-resistance, and automation requirements.

The Bell-LaPadula model enforces confidentiality through the no-read-up and no-write-down properties. The no-read-up rule prevents subjects from reading objects at a higher classification, and the no-write-down rule prevents writing to lower classifications. This directly matches the requirement to restrict reading above clearance and writing to lower levels.

Constant-time execution removes data-dependent branches and memory-access timing, while base blinding randomizes the operand and exponent blinding randomizes the private exponent value used in each operation. Together they decorrelate the power and EM traces from the actual secret key, directly defeating statistical side-channel analysis even when the attacker can physically measure the device.

Storing the public key in OTP fuses creates an immutable root of trust that cannot be altered without physical tampering. The bootloader verifies its own signature or the next stage's signature using this key, establishing a chain of trust. This ensures that only firmware signed with the corresponding private key can execute, meeting the requirements for authentication and immutability. It is a standard approach for secure boot in embedded systems.

Token validation compares the issued-at and expiry claims against the validator's own clock, so a multi-minute skew causes tokens that are genuinely valid to appear not-yet-valid or expired. Pointing both systems at the same authenticated NTP hierarchy removes the skew at its source and restores consistent validation without weakening token lifetimes.

Ephemeral Diffie-Hellman generates a unique key pair per session, then discards it, so compromising the server's long-term private key cannot decrypt past traffic — satisfying the forward secrecy requirement. Because each handshake derives fresh session keys, reuse across sessions is impossible, meeting the stem's second constraint.

Reviewing logs allows the analyst to understand the attack patterns and identify false positives. Creating custom rules tailors the WAF to the specific application, reducing false positives. Switching to blocking mode after tuning ensures that legitimate traffic is not disrupted while attacks are blocked.