4.0 Network Security N10-009 Practice Quiz

• A. Data in transit is data actively moving across a network, for example credit card numbers sent from a browser to a payment server (protected by TLS/HTTPS) or credentials sent from a branch office to headquarters (protected by IPSec VPN); data at rest is data stored on a device or media, for example customer records stored in a database (protected by AES encryption at the tablespace or column level) or an employee laptop's hard drive (protected by BitLocker or FileVault full disk encryption); both must be protected because an attacker who steals a hard drive bypasses transit encryption and an attacker who intercepts network traffic bypasses at-rest encryption
• B. Data in transit means data stored on a backup tape; data at rest means data moving through a VPN tunnel; TLS protects backup tapes and IPSec protects VPN tunnels
• C. Data in transit and data at rest are identical concepts; any data protected by AES-256 is both in transit and at rest simultaneously; the distinction is marketing terminology with no technical significance
• D. Data in transit only exists in RAM during network transmission; once written to any storage medium it becomes data at rest; TLS protects both states because it encrypts RAM buffers before data is written to disk

Both states require independent encryption controls; TLS/HTTPS and IPSec protect data moving across networks; full disk encryption and database encryption protect stored data; an attacker with physical access to storage media can bypass network encryption completely while a network eavesdropper cannot access properly encrypted stored data. This is the correct answer.

• A. A PKI certificate is signed by a trusted Certificate Authority (CA) that vouches for the binding between the certificate's public key and the claimed identity; browsers and operating systems ship with a pre-installed list of trusted root CAs so any certificate signed by those CAs is automatically trusted; a self-signed certificate is signed by the same entity that created it with no third-party vouching for the identity; browsers display security warnings for self-signed certificates because there is no trusted CA in the chain to verify the server's identity; PKI certificates provide authentication (who are you) in addition to enabling encryption; self-signed certificates enable encryption but not trusted authentication
• B. PKI certificates use RSA keys while self-signed certificates use weaker DSA keys; the signing authority determines which cryptographic algorithm is used; CA-signed certificates are always more secure because RSA is stronger than DSA
• C. Self-signed certificates are always invalid and cannot be used to establish any TLS connection; only CA-signed certificates enable HTTPS; attempting to use a self-signed certificate results in connection failure not just a warning
• D. PKI and self-signed certificates are identical in all security properties; the only difference is cost, CA-signed certificates require payment while self-signed certificates are free; organizations on tight budgets should use self-signed certificates as a full security equivalent

The chain of trust is the defining difference; CAs verify the identity of certificate requestors before signing; browsers trust CAs; therefore browsers trust CA-signed certificates transitively; self-signed certificates break this chain, there is no trusted party verifying the identity claim. This is the correct answer.

• A. TLS 1.3 is not HIPAA-approved; only TLS 1.2 satisfies HIPAA requirements; upgrading to TLS 1.2 resolves the finding and makes database encryption unnecessary
• B. The finding is incorrect; TLS 1.3 encrypts data end-to-end from browser to database including the database storage layer; the auditor has misunderstood how TLS works; no additional encryption is required
• C. TLS protects PHI only while it travels between the browser and web server; once the data arrives at the server and is written to the database it is stored in plaintext; HIPAA's Security Rule requires encryption of PHI both in transit and at rest; a database compromise, unauthorized DBA access, stolen backup tape, or misconfigured cloud storage bucket would expose all PHI without at-rest encryption; the finding requires implementing database-level encryption (transparent data encryption, column-level encryption) or application-level encryption of PHI fields before storage
• D. HIPAA does not require encryption of data at rest; the auditor is applying GDPR requirements to a HIPAA context; at-rest encryption is a GDPR requirement but HIPAA only mandates in-transit encryption through TLS

TLS terminates at the web server or load balancer; beyond that point data flows in cleartext to the database and is stored unencrypted; HIPAA's addressable implementation specification for encryption covers both states; at-rest encryption protects against the significant threat of database server compromise and backup media theft. This is the correct answer.

• A. No gap exists; the laptop's full disk encryption protects all files including those synced to cloud storage; disk encryption follows the data wherever it goes
• B. The laptop disk encryption extends to cloud-synced files because the sync agent encrypts files before uploading using the same BitLocker key; full disk encryption automatically encrypts all data leaving the device regardless of destination
• C. The gap is only a compliance issue not a technical security gap; cloud storage providers are subject to their own security standards; as long as the employee signs the provider's terms of service the data is contractually protected
• D. The employee's action creates two encryption gaps: first, if the cloud storage service does not encrypt data at rest, corporate files stored in the cloud are unencrypted at rest on the provider's servers, outside the organization's control and encryption policy; second, if the sync occurs over HTTP (or the cloud service uses weak transport security) data is unencrypted in transit during the sync; even if the laptop has full disk encryption the cloud copy is no longer protected by laptop encryption once it leaves the device; additionally the organization loses control over where the data resides (data locality violation) and who can access it; the fix involves prohibiting unauthorized cloud storage via DLP (Data Loss Prevention) policy and providing authorized encrypted cloud storage alternatives

Cloud sync creates uncontrolled copies of data outside the organization's encryption and access control perimeter; both in-transit (upload) and at-rest (cloud storage) encryption gaps may exist; DLP controls prevent this data exfiltration while authorized corporate cloud storage provides a compliant alternative. This is the correct answer.

• A. The contractor's computer has a newer browser version that does not support the company's certificate format; downgrading the contractor's browser to match the employees' version resolves the warnings
• B. The contractor is seeing warnings because their computer's clock is wrong; certificate validation checks the current time against the certificate validity period; a clock set to the wrong year causes all certificates to appear expired generating browser warnings
• C. The company's internal CA root certificate is installed in the trusted certificate store on all employee computers (via Group Policy or MDM) but has not been installed on the contractor's computer; browsers trust certificates by tracing the chain back to a root CA in their trusted store; if the internal CA root is not in the contractor's trusted store the browser cannot verify the certificate chain and displays a warning; the fix is installing the company's internal CA root certificate in the contractor's certificate store, either through Group Policy if they are domain-joined, through MDM enrollment, or manually by exporting and installing the root certificate; this is why internal CAs work seamlessly for managed devices but require additional steps for unmanaged or external devices
• D. The internal CA root certificate expired six months ago when the contractor joined; all certificates signed by an expired root CA generate warnings; the company must purchase a new commercial CA root certificate to resolve warnings for all users including employees

Root certificate distribution to managed devices via Group Policy or MDM is how internal CAs work transparently; the contractor's unmanaged device lacks the internal root CA in its trust store; this is the standard onboarding requirement for contractor devices on networks using internal PKI. This is the correct answer.

• A. Key reuse is acceptable and recommended; using the same key reduces management complexity and the same AES-256 strength protects both states equally; the developer's suggestion should be implemented
• B. Reusing encryption keys between different contexts (at-rest and in-transit) creates multiple security risks: if the key is compromised through either attack vector both protections fail simultaneously, an attacker who extracts the key from TLS traffic analysis also gains the database decryption key; TLS and AES-256 disk encryption use keys differently (TLS derives session keys from the master key through key derivation functions while disk encryption uses the key directly) making raw key reuse technically problematic; key rotation policies differ, TLS session keys should rotate frequently (per-session) while database encryption keys may rotate annually making a shared key impossible to rotate appropriately for both; cryptographic best practice (key separation) requires different keys for different purposes and different contexts; proper key management with separate keys for each purpose reduces blast radius if either key is compromised
• C. The risk is performance degradation not security; using one key for both operations causes CPU contention when the database and replication system access the same key simultaneously; separate keys eliminate the CPU bottleneck
• D. AES-256 keys cannot be used for TLS; TLS uses RSA or ECC keys exclusively; AES-256 is a symmetric algorithm incompatible with TLS which requires asymmetric encryption; the developer's suggestion is technically impossible

Key separation is a fundamental cryptographic principle; each key should have one purpose, one context, and one rotation schedule; cross-context key reuse means a single compromise breaks multiple security controls simultaneously; TLS uses keys in fundamentally different ways from symmetric storage encryption making raw key sharing technically problematic. This is the correct answer.

• A. The Issuing CA automatically renews its own certificate from the Root CA through an online renewal protocol; no human intervention is needed; the 30-day warning is informational only and the renewal completes automatically before expiration
• B. The Issuing CA can self-renew its certificate without the Root CA; the renewal is performed by the Issuing CA signing its own new certificate using its existing private key; this is called a subordinate self-renewal and is the standard procedure for two-tier PKI hierarchies
• C. The Root CA is kept offline to reduce electricity costs; an offline server uses no power; the renewal procedure involves purchasing a new commercial root certificate from a public CA to replace the expiring Issuing CA certificate
• D. Renewal procedure: bring the offline Root CA online in a controlled environment (air-gapped workstation or HSM), generate a new certificate signing request from the Issuing CA, sign the new Issuing CA certificate with the Root CA private key, install the new certificate on the Issuing CA, publish the new certificate to the CA repository, then take the Root CA offline again; the Root CA is kept offline because it is the ultimate trust anchor for the entire PKI, if the Root CA private key is compromised every certificate in the organization becomes untrustworthy and the entire PKI must be rebuilt from scratch; keeping it offline (air-gapped) means it is never exposed to network-based attacks; it only comes online for the rare operations of signing Issuing CA certificates; the Issuing CA handles day-to-day certificate issuance and its compromise while serious can be remediated without rebuilding the entire PKI

The offline Root CA protects the PKI's ultimate trust anchor; the Issuing CA's controlled renewal from the offline Root CA is a formal security procedure that should be documented in a Certificate Practice Statement; the infrequency of Root CA operations (only for Issuing CA certificate renewal every few years) justifies the offline complexity. This is the correct answer.

• A. Accepting certificates from any CA is the correct default behavior; browsers maintain a list of hundreds of trusted CAs and trusting all of them provides maximum compatibility; restricting to specific CAs would break connectivity for many users
• B. This reveals that the application does not implement certificate pinning or CA restriction; accepting certificates from any trusted CA means an attacker who can create a certificate from any of the hundreds of trusted CAs (through a compromised CA, a rogue CA, or a government-mandated CA interception) can perform a man-in-the-middle attack against the application; additionally the tester's own test CA should not be trusted by the application at all; fixes include: implementing certificate pinning (hardcoding the expected certificate or public key in the application) for high-security internal applications, configuring CAA (Certification Authority Authorization) DNS records to restrict which CAs can issue certificates for the domain, and for mobile or internal applications using a private CA and distributing only that CA's root reducing the trusted CA set to one; the broader browser ecosystem relies on CA/Browser Forum rules to police CAs but application-level controls provide stronger guarantees
• C. The vulnerability is that TLS is enabled; disabling TLS and using plaintext HTTP eliminates certificate-related vulnerabilities; certificate management is more complex than the security benefit justifies for internal applications
• D. This reveals that the application uses TLS 1.0 which accepts certificates from any CA; upgrading to TLS 1.3 restricts certificate acceptance to approved CAs only; TLS version determines which CAs are trusted

Unrestricted CA acceptance is a meaningful attack surface; CAA records and certificate pinning provide layered controls; a rogue or compromised CA can issue valid-appearing certificates for any domain; application-specific CA restrictions reduce this risk for sensitive systems. This is the correct answer.