General Security Concepts

268 questions

Question 141Question

An organization is updating its enterprise risk management framework and classifying its existing defense mechanisms according to CompTIA Security+ control categories. The Chief Information Security Officer (CISO) requests an inventory of all Managerial (Administrative) controls currently implemented across the company. Which of the following defense mechanisms qualify as Managerial controls? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Performing annual third-party vendor risk assessments to evaluate supply chain security risks; Establishing an enterprise-wide Acceptable Use Policy (AUP) approved by executive management

Answer

Performing annual third-party vendor risk assessments and establishing an enterprise-wide Acceptable Use Policy (AUP) are both Managerial controls.
Both vendor risk assessments and acceptable use policies focus on governance, administrative oversight, and risk strategy. Under CompTIA Security+, controls designed around management decisions, policies, and risk assessments are categorized as Managerial (Administrative) controls.

Step-by-Step Solution

1
Analyze the definition of Managerial controls under CompTIA Security+.
Managerial (Administrative) controls focus on security governance, risk assessment, policies, oversight, and strategic guidelines.
Control categorization depends on how the control is designed and managed within the organizational governance framework.
2
Evaluate each option against the Managerial category criteria.
Third-party risk assessments evaluate organizational risk (Managerial). Acceptable Use Policies set governance rules (Managerial). Firewalls rely on technological mechanisms (Technical). Security guard patrols rely on operational human workflows (Operational).
Differentiating control categories ensures proper assignment of security responsibility and compliance reporting.

Key Concept

Security Control Categories (Managerial / Administrative Controls)
Estimated Time:1m 15s
Question 142Question

Following an internal audit that identified unauthorized workstation software modifications, an enterprise security team deploys an automated configuration management tool. This software continuously monitors workstation configuration files against an established baseline and automatically restores any modified settings back to their approved baseline state. Which of the following best classifies this security control according to CompTIA Security+ category and functional type definitions?

Show answer & explanation

Answer: Technical category and Corrective type

Answer

Technical category and Corrective type
The security mechanism is classified under the Technical (Logical) category because it is executed by automated software logic and system monitoring tools. It is classified under the Corrective functional type because its primary objective is to reverse unauthorized modifications and restore the system back to its known-good baseline state following an incident.

Step-by-Step Solution

1
Determine the implementation category based on how the control is enforced.
The control is implemented via automated software logic and system configuration tools, placing it in the Technical (Logical) category.
Technical controls use hardware, software, or firmware mechanisms to execute security functions automatically.
2
Analyze the functional outcome of the control when triggered by an unauthorized change.
The tool automatically reverses unauthorized modifications and restores systems to their compliant baseline state.
Functional types that repair damage, reverse unauthorized changes, or restore systems to operational baselines are classified as Corrective controls.
3
Combine the implementation category and functional type.
The mechanism is correctly classified as a Technical category control executing a Corrective functional type.
Combining automated technical execution with post-modification restoration aligns with Technical and Corrective definitions.

Key Concept

Security Control Categories and Functional Types
Estimated Time:1m 15s
Question 143Question

Match each enterprise security implementation to its primary CompTIA Security+ classification by category and functional type.

Click a left item, then click its matching right item

Items

Installing motion-activated floodlights and warning signs along the perimeter fence line of a remote data center facility.
Deploying a host-based file integrity monitoring (FIM) agent to inspect critical system files for unauthorized changes.
Formalizing an enterprise incident response policy and standard operating procedures (SOPs) mandated by management.
Executing automated endpoint quarantine and running malware cleanup scripts to restore infected systems back to a known good state.

Matches

Show answer & explanation

Answer

1. Installing motion-activated floodlights and warning signs matches Physical / Deterrent.
2. Deploying host-based file integrity monitoring (FIM) matches Technical / Detective.
3. Formalizing an enterprise incident response policy and SOPs matches Managerial / Directive.
4. Executing automated endpoint quarantine and malware cleanup scripts matches Technical / Corrective.
Each security implementation correctly pairs its underlying mechanism (category: Technical, Managerial, Operational, Physical) with its operational purpose (functional type: Preventive, Deterrent, Detective, Corrective, Compensating, Directive) according to standard CompTIA Security+ SY0-701 guidelines.

Step-by-Step Solution

1
Analyze the physical perimeter control (floodlights and signage).
Identified as a physical mechanism (Physical category) intended to discourage attackers before an action occurs (Deterrent functional type).
Physical elements protecting tangible assets that discourage breach attempts align with Physical / Deterrent.
2
Analyze the host-based software control (File Integrity Monitoring).
Identified as a system/software mechanism (Technical category) designed to discover anomalous modifications (Detective functional type).
Software-driven monitoring tools that alert on system compromise function as Technical / Detective controls.
3
Analyze the governance document (incident response policy and SOPs).
Identified as administrative oversight (Managerial category) that mandates expected security practices (Directive functional type).
Framework policies set by leadership to dictate compliant behavior are Managerial / Directive.
4
Analyze the remediation action (quarantine and cleanup scripts).
Identified as a software automated response (Technical category) aimed at reversing harm and restoring operations (Corrective functional type).
Automated technical actions taken post-incident to fix compromised endpoints fit Technical / Corrective.

Key Concept

Classification of Security Control Categories (Technical, Managerial, Operational, Physical) and Functional Types (Preventive, Deterrent, Detective, Corrective, Compensating, Directive)
Question 144Question

An enterprise security administrator is establishing a Public Key Infrastructure (PKI) key lifecycle policy for employee S/MIME email certificates. The policy specifies that private keys associated with email encryption certificates must be backed up to a key escrow agent, whereas private keys associated with digital signature certificates are strictly prohibited from key escrow. Which of the following best explains the security rationale for prohibiting key escrow on digital signature private keys?

Show answer & explanation

Answer: Escrowing signature private keys violates non-repudiation because authorized escrow administrators could technically forge a user's digital signature.

Answer

Escrowing signature private keys violates non-repudiation because authorized escrow administrators could technically forge a user's digital signature.
Digital signatures guarantee non-repudiation, which requires sole control over the signing private key. Archiving or escrowing a signature private key means another party (such as a system administrator or key recovery agent) could potentially use that key to sign documents or emails, thereby destroying the legal proof of non-repudiation.

Step-by-Step Solution

1
Analyze the dual-key requirement in PKI deployment for S/MIME.
S/MIME uses two distinct key pairs: one pair for bulk data encryption/decryption and one pair for digital signatures.
Encryption keys require backup/escrow to recover encrypted business data if an employee leaves or loses access. Signature keys serve a different security purpose.
2
Evaluate the impact of key escrow on the security properties of digital signatures.
Digital signatures guarantee authenticity, integrity, and non-repudiation.
Non-repudiation mandates that only the single private key owner could have signed the document. If any third party or escrow agent has access to the private key, the owner can plausibly claim someone else signed it.

Key Concept

Key Escrow vs. Non-Repudiation in PKI Dual-Key Management
Question 145Question

A security architect is deploying TLS certificates for three newly established internal microservices hosted on distinct domain structures: identity.corp.local, billing.corp.internal, and api.corp.com. To simplify management, the architect intends to issue a single digital certificate that will be trusted and valid across all three different fully qualified domain names. Which of the following configuration options should the security architect specify during certificate generation to achieve this goal?

Show answer & explanation

Answer: Subject Alternative Name (SAN) extension

Answer

The Subject Alternative Name (SAN) extension should be specified in the certificate request.
The correct option is the Subject Alternative Name (SAN) extension. SAN is an X.509 extension that allows security professionals to specify multiple hostnames, IP addresses, or domain names (including different top-level domains) in a single SSL/TLS certificate.

Step-by-Step Solution

1
Analyze the technical requirements of the scenario.
The requirement demands securing three distinct domain names (identity.corp.local, billing.corp.internal, and api.corp.com) using a single digital certificate.
Different domain names with varied top-level domains cannot be covered by standard single-domain certificates or wildcard certificates.
2
Evaluate PKI certificate extension options for multi-domain support.
The Subject Alternative Name (SAN) X.509 extension field explicitly allows multiple discrete hostnames and domain names to be embedded within a single certificate.
SAN extensions provide flexible identity binding across unrelated domain structures.

Key Concept

Subject Alternative Name (SAN) Certificates
Estimated Time:1m 15s
Question 146Question

An enterprise organization is replacing its legacy perimeter-based defenses with a Zero Trust Architecture (ZTA) across its internal API microservices. Currently, services authenticate once at session initiation and receive unrestricted inter-service communication permissions across the internal subnet. Which design change must the security team implement to adhere to core Zero Trust principles?

Show answer & explanation

Answer: Enforce dynamic continuous verification of identity, device posture, and context for every request, regardless of whether the traffic originates internally.

Answer

Enforce dynamic continuous verification of identity, device posture, and context for every request, regardless of whether the traffic originates internally.
The core tenets of Zero Trust Architecture (NIST SP 800-207) mandate explicit validation and continuous verification. Every access request must be authenticated, authorized, and encrypted based on real-time contextual data, identity, and device health, regardless of whether the request originates inside or outside the traditional network perimeter.

Step-by-Step Solution

1
Analyze current system weaknesses
Identified implicit trust after initial session authentication across internal microservices.
Legacy architectures rely on perimeter trust, allowing lateral movement once inside.
2
Apply Zero Trust Architecture (ZTA) core principles
Determine that all requests must be explicitly validated and continuously authorized.
Zero Trust operates under the assumption of breach and treats all network segments as potentially untrusted.
3
Select the compliant design modification
Requiring per-request continuous verification of identity, device posture, and contextual variables.
This removes implicit internal trust and enforces microsegmentation and continuous authorization.

Key Concept

Zero Trust Architecture Principles - Explicit Validation and Continuous Verification
Question 147Question

An enterprise organization is modernizing its security framework by implementing Zero Trust Architecture (ZTA) principles across its hybrid multi-cloud infrastructure. To validate the deployment, the lead security architect must map foundational Zero Trust principles to their specific technical operational mechanisms. Match each Zero Trust Architecture principle on the left with its correct technical implementation mechanism on the right.

Click a left item, then click its matching right item

Items

Continuous Explicit Verification
Microsegmentation and Blast Radius Reduction
Assume Breach and Least Privilege Access
Control Plane and Data Plane Separation

Matches

Show answer & explanation

Answer

Continuous Explicit Verification matches with dynamically re-evaluating credentials, device posture, and context on every request. Microsegmentation and Blast Radius Reduction matches with enforcing workload-to-workload application layer controls and mTLS to prevent lateral movement. Assume Breach and Least Privilege Access matches with restricting access through just-in-time ephemeral credentials. Control Plane and Data Plane Separation matches with decoupling policy decision engines from inline data inspection gateways.
The correct pairings accurately reflect NIST SP 800-207 Zero Trust tenets. Continuous Explicit Verification ensures ongoing dynamic checks per request rather than static login. Microsegmentation prevents internal lateral movement by dividing resources into granular zones using mTLS. Assume Breach limits threat impact by combining minimal access rights with short-lived tokens. Control Plane and Data Plane separation distinguishes decision-making logic from traffic enforcement gateways.

Step-by-Step Solution

1
Analyze Continuous Explicit Verification
Identified that Zero Trust mandates 'never trust, always verify', requiring real-time contextual validation per transaction.
Initial login status or network location cannot grant implicit trust for subsequent transactions.
2
Analyze Microsegmentation and Blast Radius Reduction
Matched with application-level isolate controls such as mTLS and software-defined perimeters.
Legacy flat networks allow unchecked lateral movement; microsegmentation contains breaches within tight boundaries.
3
Analyze Assume Breach and Least Privilege Access
Matched with just-in-time (JIT) temporary access tokens providing minimal scope.
Designing for compromise requires minimizing rights granted to users or services to limit damage.
4
Analyze Control Plane and Data Plane Separation
Matched with separating policy decision engines (PE/PA) from inline traffic proxies (PEP).
Logical separation ensures management and policy evaluation remain isolated from physical data movement.

Key Concept

Zero Trust Architecture Operational Principles
Question 148Question

A security architecture team is designing an active defense strategy to detect threat actors performing lateral movement within a cloud-hybrid network. The team specifically wants to plant decoy authentication credentials into workstation memory and local caches so that any credential dumping attempt immediately generates high-fidelity alerts without exposing production directory services. Which of the following deception technologies best fulfills this operational requirement?

Show answer & explanation

Answer: Placing honeytokens within endpoint credential caches to act as decoy authentication material that alerts security operations upon access

Answer

Placing honeytokens within endpoint credential caches to act as decoy authentication material that alerts security operations upon access
Honeytokens (and breadcrumbs) are fake credentials, tokens, or data planted in places like LSASS memory, configuration files, or credential managers. When an attacker attempts to harvest and use these decoy credentials, security systems generate high-confidence alerts, detecting lateral movement early without placing actual production directory services at risk.

Step-by-Step Solution

1
Analyze the operational objective of the scenario
The goal is to detect credential dumping and lateral movement attempts by placing fake/decoy credentials directly into endpoint memory or local caches.
Understanding the requirement isolates active deception mechanisms from traditional preventive controls.
2
Evaluate the deception technology options against the required asset type
Decoy credentials, fake API keys, or embedded breadcrumbs used to lure attackers are classified as honeytokens.
Honeytokens specifically target data and credential lures, whereas honeypots are full decoy systems or services.
3
Differentiate honeytokens from traditional network and host controls
Preventive controls like microsegmentation or inline IPS block actions rather than serving as deceptive traps that yield early threat intelligence.
Deception tools deliberately allow the attacker to interact with fake data to signal malicious presence.

Key Concept

Deception Technologies (Honeytokens and Breadcrumbs)
Question 149Question

A security engineer is updating the cryptographic configuration of an internal API gateway to enhance session transport security. The new security baseline requires providing Perfect Forward Secrecy (PFS) for key establishment and guaranteeing message authentication and integrity for incoming payload headers. Which TWO cryptographic mechanisms or algorithms should the security engineer implement to satisfy these requirements?

Select all that apply

Show answer & explanation

Answer: Elliptic Curve Diffie-Hellman Ephemeral (ECDHE); Hash-based Message Authentication Code with SHA-256 (HMAC-SHA256)

Answer

The security engineer should implement Elliptic Curve Diffie-Hellman Ephemeral (ECDHE) for key establishment and HMAC-SHA256 for header integrity and authentication.
Elliptic Curve Diffie-Hellman Ephemeral (ECDHE) provides dynamic key exchange where session keys are temporary and discarded after use, guaranteeing Perfect Forward Secrecy. HMAC-SHA256 pairs a secret cryptographic key with a hash function, ensuring both message integrity and sender origin authentication.

Step-by-Step Solution

1
Analyze key establishment requirements for Perfect Forward Secrecy (PFS).
Identify that ephemeral key exchange mechanisms like ECDHE regenerate key pairs per session, preventing retroactive decryption.
Static asymmetric key exchanges like static RSA decrypt session secrets using long-term private keys, violating PFS principles.
2
Analyze payload header requirements for message authenticity and integrity.
Identify that symmetric keyed hashing (HMAC-SHA256) verifies both data integrity and origin authenticity.
Unkeyed hash functions verify integrity against corruption but cannot authenticate the sender, while plain symmetric ciphers without MAC tags only provide confidentiality.

Key Concept

Cryptographic Concepts and Algorithms
Question 150Question

An enterprise security architect is auditing a remote access workflow designed for external software developers. Under the proposed model, after a developer successfully completes multi-factor authentication (MFA) at the edge gateway, their endpoint is assigned an IP address on the internal development network segment. From that point forward, the session maintains open access to all internal repository servers and staging databases without requiring further authentication or posture checks until disconnect. Which of the following best evaluates this architecture against Zero Trust Architecture (ZTA) principles and identifies the necessary architectural remediation?

Show answer & explanation

Answer: The design violates Zero Trust by granting implicit perimeter trust following initial authentication; access must be continuously evaluated and authorization granted per resource request using microsegmentation.

Answer

The proposed architecture violates Zero Trust principles by granting implicit network-level trust after initial authentication. It must be updated to enforce continuous validation and microsegmentation for every individual resource request.
Zero Trust Architecture operates on the fundamental principle that implicit trust must be eliminated ('never trust, always verify'). Granting broad access to internal network segments based on a single initial perimeter authentication violates this principle. The correct architecture requires continuous validation of identity, device health, and environmental context, paired with microsegmentation so that access is restricted explicitly to individual requested resources.

Step-by-Step Solution

1
Analyze the proposed access flow against NIST SP 800-207 Zero Trust Architecture core tenets.
Identified that once the initial MFA check succeeds, the user endpoint is granted persistent network-wide access to internal repository and database servers.
Zero Trust mandates that no implicit trust is granted based solely on physical or logical network location or initial perimeter authentication.
2
Evaluate the architectural flaw.
The reliance on a legacy perimeter model (VLAN assignment post-MFA) allows lateral movement if the endpoint or credentials become compromised during the active session.
Access policies in Zero Trust must be granular, dynamic, and evaluated per request rather than maintaining a persistent state across an broad network segment.
3
Select the appropriate Zero Trust remediation strategy.
Implement continuous verification (evaluating identity, device health, and context dynamically) and microsegmentation (restricting visibility and path to specific requested resources only).
This enforces explicit validation and limits the blast radius of any potential compromise.

Key Concept

Zero Trust Architecture - Implicit Trust Elimination and Continuous Verification
Question 151Question

An organization implements digital signatures for all high-value financial transactions to ensure that executives cannot deny approving a transaction after it has been submitted. Which security goal is primarily being addressed by this implementation?

Show answer & explanation

Answer: Non-repudiation

Answer

Non-repudiation is the primary security goal addressed by using digital signatures to prevent users from denying their actions.
Non-repudiation ensures that an individual cannot deny the authenticity of their signature or action on a document or transaction. Digital signatures achieve this by utilizing asymmetric key cryptography, where the signer's unique private key creates a signature that anyone can verify using the corresponding public key.

Step-by-Step Solution

1
Analyze the scenario requirements
The core requirement is preventing an executive from denying that they approved a transaction.
Identifying the goal of preventing denial of an origin or action leads to the appropriate security concept.
2
Map the technical control to security objectives
Digital signatures bind sender identity verification with data integrity verification.
Combining sender identity proof via a private key with integrity verification guarantees proof of origin.
3
Select the matching security objective
Non-repudiation directly defines the property where a party to a transaction cannot deny authenticity.
Non-repudiation specifically satisfies the requirement of undeniable proof of origin and action.

Key Concept

Non-Repudiation
Estimated Time:45s
Question 152Question

A healthcare organization requires that when physicians approve electronic prescription orders, the system must generate proof of origin so that a physician cannot later deny authorizing the order. To accomplish this, the system applies a digital signature using the physician's private key combined with a cryptographic hash of the order details. Which security concept is directly fulfilled by implementing digital signatures to prevent denial of origin?

Show answer & explanation

Answer: Non-repudiation

Answer

Non-repudiation is the primary security goal achieved, as digital signatures bind an identity to a specific transaction using asymmetric cryptography so the sender cannot deny authorizing it.
The correct concept is non-repudiation. Digital signatures combine asymmetric cryptography (signing with the sender's private key) and cryptographic hashing to provide both authenticity of origin and data integrity. Because only the physician possesses their private key, they cannot claim a signed order was generated by someone else.

Step-by-Step Solution

1
Analyze the scenario requirement
The scenario requires preventing an individual (the physician) from denying that they approved a specific electronic prescription order.
Identifying the core business and security goal isolates which security pillar or principle is being tested.
2
Evaluate the technical control described
The control uses asymmetric key pairs (private key signing) combined with a cryptographic hash of the payload.
A cryptographic hash guarantees integrity (tamper-resistance), while signing with a private key uniquely ties the data to the key holder's identity.
3
Map the technical control to the core security concept
Combining integrity verification with cryptographic proof of identity yields non-repudiation.
Non-repudiation ensures that a party to a contract or communication cannot successfully challenge the authenticity of their signature or transaction.

Key Concept

Non-repudiation and CIA Triad
Question 153Question

An enterprise security team is transitioning network operations to align with Zero Trust Architecture (ZTA) principles. Which of the following statements accurately describes a fundamental principle of access control within Zero Trust?

Show answer & explanation

Answer: Every access request must be explicitly validated and continuously authorized based on contextual attributes, regardless of whether the connection originates inside or outside the corporate network.

Answer

Every access request must be explicitly validated and continuously authorized based on contextual attributes, regardless of whether the connection originates inside or outside the corporate network.
The correct principle mandates that no user, device, or network segment is trusted by default. Every access request must be explicitly validated and continuously authorized using real-time contextual context regardless of location.

Step-by-Step Solution

1
Identify the core tenet of Zero Trust Architecture
Zero Trust assumes that threats exist both outside and inside the traditional network boundary.
Legacy perimeter security relies on implicit trust within the internal network, whereas Zero Trust operates on the baseline assumption of zero implicit trust.
2
Evaluate access control enforcement mechanisms in Zero Trust
Access decisions must be explicitly verified, applying least privilege access dynamically based on context (user, device, location, asset value).
Continuous authentication and explicit verification ensure that moving inside the network perimeter does not grant unverified access.

Key Concept

Zero Trust Architecture Principles - Never Trust, Always Verify
Estimated Time:45s
Question 154Question

Match each core security goal or concept on the left with its primary operational objective on the right.

Click a left item, then click its matching right item

Items

Confidentiality
Integrity
Availability
Non-Repudiation

Matches

Show answer & explanation

Answer

Confidentiality matches preventing unauthorized disclosure; Integrity matches safeguarding data against unauthorized alteration; Availability matches ensuring data accessibility when needed; Non-Repudiation matches providing unalterable proof of an action.
Each security term directly corresponds to its foundational definition: Confidentiality protects against unauthorized exposure, Integrity prevents unauthorized alteration, Availability ensures operational access, and Non-Repudiation provides indisputable proof of origin or action.

Step-by-Step Solution

1
Define the primary purpose of Confidentiality.
Confidentiality restricts data access to authorized entities.
Protects sensitive data from unauthorized disclosure.
2
Define the primary purpose of Integrity.
Integrity maintains data accuracy and trustworthiness.
Prevents unauthorized modification, deletion, or tampering.
3
Define the primary purpose of Availability.
Availability ensures uptime and accessibility.
Guarantees services and data are ready for authorized use.
4
Define the primary purpose of Non-Repudiation.
Non-Repudiation binds an action to a specific identity cryptographic proof.
Prevents a party from falsely claiming they did not perform a given action.

Key Concept

Core definitions of the CIA Triad pillars and Non-Repudiation
Question 155Question

A financial software firm secures its system log repository by encrypting log files with AES-256 and generating an HMAC-SHA256 checksum for each entry using a shared secret key accessible by all system administrators. During an investigation into an unauthorized privilege escalation, a senior administrator is suspected of editing log lines to erase evidence. The administrator claims that another employee with administrative credentials must have altered the logs using the shared key. Which security property is currently lacking in the firm's audit system that prevents proving which specific administrator committed the modification?

Show answer & explanation

Answer: Non-repudiation, because shared secret keys cannot uniquely attribute actions to a specific individual user.

Answer

The audit system lacks non-repudiation because shared secret keys permit any key holder to create valid HMAC tags, preventing positive cryptographic attribution to a specific individual.
Non-repudiation ensures that a specific subject cannot deny having performed an action or created a message. Because HMAC relies on a symmetric key shared among multiple administrators, any key holder can forge a valid HMAC tag. To achieve non-repudiation, the organization must use asymmetric cryptography (digital signatures) using unique private keys held by each individual administrator.

Step-by-Step Solution

1
Analyze the cryptographic mechanisms used in the logging system.
AES-256 provides confidentiality, and HMAC-SHA256 provides data integrity and group origin verification.
HMAC relies on symmetric shared secrets across all authorized administrators.
2
Evaluate why the administrator can plausibly deny performing the action.
Since all system administrators possess the shared key, any administrator could generate a valid HMAC tag for a modified log entry.
Symmetric keys cannot differentiate between distinct holders of the same secret.
3
Identify the missing security goal required for individual accountability.
Non-repudiation is missing; implementing asymmetric digital signatures with private keys assigned strictly to individual administrators would solve this.
Digital signatures provide non-repudiation by binding an action uniquely to one private key holder.

Key Concept

CIA Triad and Non-Repudiation (Symmetric HMAC vs Asymmetric Digital Signatures)
Question 156Question

An enterprise API gateway receives automated configuration updates from external vendors. To satisfy auditing requirements, security policies dictate that the system must establish indisputable proof of origin for every payload, ensuring vendors cannot deny sending a specific update. The system architects propose utilizing SHA-256 hashing paired with pre-shared symmetric keys (HMAC) between the gateway and each vendor. Which security goal remains unfulfilled by this proposed architecture, and why?

Show answer & explanation

Answer: Non-repudiation, because symmetric shared keys allow either the sender or receiver to generate a valid message authentication code, preventing third-party proof of origin.

Answer

Non-repudiation remains unfulfilled because symmetric pre-shared keys allow either party possessing the key to create a valid HMAC, preventing proof of payload origin to a third-party auditor.
Non-repudiation requires unforgeable proof of origin that can be verified by a third party. Because symmetric HMAC relies on a secret key known to both the sender and the receiver, either party can compute the valid hash. Therefore, the vendor can plausibly claim the receiver generated the hash, failing non-repudiation. Asymmetric digital signatures (private key signing) are required to achieve non-repudiation.

Step-by-Step Solution

1
Analyze the security requirement stated in the scenario.
The scenario requires indisputable proof of origin so vendors cannot deny sending a specific payload (non-repudiation).
Non-repudiation provides legal or technical proof that a specific sender created and transmitted a message.
2
Evaluate the proposed cryptographic mechanism (SHA-256 HMAC with pre-shared symmetric keys).
Symmetric HMAC keys are known to both the vendor (sender) and the enterprise API gateway (receiver).
Because both parties hold the identical secret key, either side could theoretically generate the matching HMAC digest.
3
Determine which security pillar is missing.
While HMACs satisfy integrity and data origin authentication between two mutually trusting endpoints, they fail to provide non-repudiation to an external auditor.
True non-repudiation requires asymmetric cryptography (digital signatures using private keys) where only the sender possesses the signing key.

Key Concept

Non-repudiation vs. Integrity in Cryptographic Mechanisms
Estimated Time:1m 30s
Question 157Question

Match each enterprise security technical implementation to the specific security pillar or concept it primarily satisfies.

Click a left item, then click its matching right item

Items

Confidentiality
Integrity
Availability
Non-Repudiation

Matches

Show answer & explanation

Answer

Confidentiality matches encrypting sensitive customer records; Integrity matches generating SHA-256 checksums for binaries; Availability matches deploying redundant power and load-balanced clusters; Non-Repudiation matches signing executive transfer requests with asymmetric private keys.
Each control satisfies a specific pillar: encryption prevents disclosure (Confidentiality); hashing detects unauthorized changes (Integrity); hardware redundancy maintains system access (Availability); private key signing binds identity to transactions (Non-Repudiation).

Step-by-Step Solution

1
Determine the security goal of encryption at rest.
Encryption restricts reading data to keyholders, satisfying Confidentiality.
Confidentiality focuses on preventing unauthorized disclosure of information.
2
Analyze the function of cryptographic checksums (SHA-256).
Hashing detects any modification in transit or storage, satisfying Integrity.
Integrity guards against unauthorized data modification or corruption.
3
Evaluate the purpose of dual power feeds and server clustering.
Redundancy mitigates single points of failure to maintain uptime, satisfying Availability.
Availability ensures hardware and software systems remain operational and accessible.
4
Identify the protection provided by asymmetric private key signatures.
Digital signatures bind identity to data so authorship cannot be refuted, satisfying Non-Repudiation.
Non-repudiation prevents an entity from denying their prior actions or messages.

Key Concept

CIA Triad and Non-Repudiation core principles and technical controls
Question 158Question

An enterprise logistics company requires software engineers to digitally sign all infrastructure configuration files using their individual asymmetric private keys before pushing them to the automated build pipeline. If an unapproved configuration change causes a service outage, management must be able to indisputably prove which specific engineer authored and submitted the change. Which security principle is primarily fulfilled by this implementation?

Show answer & explanation

Answer: Non-repudiation

Answer

Non-repudiation
Non-repudiation ensures that a sender or author cannot deny the authenticity of their signature on a document or file. By requiring engineers to sign configuration files with their asymmetric private keys, the system creates proof of origin linked uniquely to that individual.

Step-by-Step Solution

1
Analyze the core requirement presented in the scenario.
Management needs to indisputably identify which engineer authored a specific file change so that the author cannot deny responsibility.
Identifying the specific requirement helps distinguish between general data protection goals and specific cryptographic properties.
2
Evaluate the mechanism used (asymmetric key digital signatures).
Signing data with a private key uniquely binds that specific identity to the generated signature.
Because only the holder possesses the private key, valid signatures provide indisputable proof of origin.
3
Map the mechanism and requirement to the standard security goal.
Providing proof of origin to prevent denial of an action is the exact definition of non-repudiation.
Non-repudiation combines authenticity and integrity via asymmetric cryptography to ensure accountability.

Key Concept

Non-Repudiation
Question 159Question

A software distribution platform requires package maintainers to cryptographically sign all published updates. This ensures that a maintainer cannot later deny having created and released a specific update package. Which of the following security concepts is best demonstrated by this requirement?

Show answer & explanation

Answer: Non-repudiation

Answer

Non-repudiation
Non-repudiation provides proof of the origin and authenticity of data, ensuring that an individual or entity cannot deny having performed a specific action, such as creating or signing a software update package.

Step-by-Step Solution

1
Analyze the scenario requirement.
The requirement mandates signing software updates so maintainers cannot deny creating and releasing them.
Identifying the core goal (preventing denial of an action) isolates the security principle being applied.
2
Map the requirement to fundamental security principles.
Providing cryptographic proof of origin to prevent denial of authorship defines non-repudiation.
Digital signatures associate an identity with specific data to enforce accountability and non-repudiation.

Key Concept

CIA Triad and Non-Repudiation
Question 160Question

An industrial smart grid operator manages several automated telemetry, control, and audit subsystems. Match each operational security scenario on the left with the primary CIA triad pillar or related security objective that is either violated or enforced on the right.

Click a left item, then click its matching right item

Items

An adversary intercepting unencrypted microwave radio links between electrical substations to read operational load and power usage metrics.
An attacker deploying a distributed flood against grid control gateways, delaying emergency shutdown signals during a transformer failure.
A malicious actor modifying calibration data within a remote terminal unit (RTU) database, leading to inaccurate telemetry without disrupting connectivity.
A chief engineer authorizing a critical relay logic patch using their private key and smart card, enabling auditors to indisputably attribute the change.

Matches

Show answer & explanation

Answer

1. Intercepting unencrypted microwave links → Confidentiality
2. Flooding control gateways during emergency → Availability
3. Modifying RTU database calibration data → Integrity
4. Signing relay logic patches with a private key → Non-Repudiation
Each scenario maps to its core security objective based on the nature of the threat or control. Unauthorized data viewing targets Confidentiality; blocking system access targets Availability; unauthorized data modification targets Integrity; and cryptographically proving the origin of an update enforces Non-Repudiation.

Step-by-Step Solution

1
Analyze the microwave eavesdropping scenario.
Unauthorized exposure of power usage metrics to outside eavesdroppers compromises data secrecy.
Protecting data from unauthorized disclosure is the definition of Confidentiality.
2
Analyze the network flood attack scenario.
Emergency shutdown communications are blocked or delayed due to system resource exhaustion.
Ensuring timely and reliable access to systems and data is the definition of Availability.
3
Analyze the calibration database alteration scenario.
Data is tampered with and corrupted while remaining operational.
Maintaining the accuracy, completeness, and uncorrupted state of data is the definition of Integrity.
4
Analyze the digitally signed engineering patch scenario.
The engineer's unique private key creates cryptographic proof of origin that cannot be refuted.
Providing proof of origin and authenticity that prevents an entity from denying an action constitutes Non-Repudiation.

Key Concept

Core Pillars of Information Security (CIA Triad) and Non-Repudiation
PreviousPage 8 / 14Next
General Security Concepts Practice Questions — CompTIA Security+ — Page 8 | Examkin