General Security Concepts

268 soru

Soru 1Soru

A cybersecurity team is deploying deception and disruption technologies within a cloud-native software development environment to detect early-stage credential access and lateral movement. Which of the following components and operational practices should the security team implement to achieve high-fidelity alerting without interfering with legitimate production workflows? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Embed non-functional synthetic API keys (honeytokens) into code repositories that generate alerts upon any authorization attempt.; Deploy low-interaction decoy container endpoints on isolated microsegments to simulate high-value internal management services.

Cevap

The correct practices are embedding non-functional synthetic API keys (honeytokens) into code repositories to alert on any access attempt, and deploying low-interaction decoy container endpoints on isolated network segments to detect probing without risking production infrastructure.
Deception strategies rely on deploying assets that serve no legitimate business purpose. The option stating that non-functional synthetic API keys (honeytokens) should be placed in code repositories is correct because any interaction with these keys immediately signals unauthorized discovery or credential harvesting. The option recommending low-interaction decoy container endpoints on isolated microsegments is also correct because it provides a lightweight decoy target to capture lateral movement probes without exposing production systems.

Adım Adım Çözüm

1
Analyze the goal of deception technologies in a cloud environment.
Identified that deception mechanisms (like honeytokens and decoys) aim to lure adversaries into interacting with non-production assets to produce high-confidence alerts.
Deception assets have no legitimate operational traffic, making any interaction suspicious.
2
Evaluate the proposed deception components against production safety and intent.
Selected honeytokens in code repositories and low-interaction decoy containers as proper deception tools.
Honeytokens detect credential misuse, and low-interaction containers catch scanning and discovery efforts safely.
3
Differentiate deception tools from standard inline prevention and filtering controls.
Disqualified inline traffic filtering and DNS dropping controls.
Honeypots do not act as inline filtering devices, and DNS filtering is a preventive control rather than a deception technology.

Anahtar Kavram

Deception and Disruption Technologies Deployment
Tahmini Süre:1m 30s
Soru 2Soru

An organization requires department managers to perform quarterly user access reviews by manually evaluating account permissions and verifying that assigned rights match current job responsibilities. Which of the following best classifies both the security control category and functional type of this process?

Cevabı ve açıklamayı göster

Cevap: Operational category and Detective functional type

Cevap

Operational category and Detective functional type
The correct answer is 'Operational category and Detective functional type'. Under the CompTIA Security+ framework, Operational controls refer to security measures implemented and executed by people through daily procedures and administrative operations. Periodic user access certification conducted by department managers is an operational process. Functionally, reviewing account rights identifies unauthorized permissions or privilege accumulation (privilege creep) that has already occurred, making it a Detective control.

Adım Adım Çözüm

1
Determine the security control category
Operational control category
Control categories in CompTIA Security+ SY0-701 are divided into Technical, Managerial, Operational, and Physical. Routine day-to-day security procedures executed by human staff and managers—such as manual log reviews or quarterly user permission audits—fall under the Operational category.
2
Determine the functional type of the control
Detective functional type
Functional types define the operational goal of the control (Preventive, Detective, Corrective, Deterrent, Compensating, Directive). Auditing existing user rights allows organizations to uncover privilege creep or non-compliant permissions after they have been granted, fulfilling a Detective function.
3
Combine category and functional type to identify the correct classification
Operational category and Detective functional type
Combining the category determined in Step 1 with the functional type determined in Step 2 yields Operational category and Detective functional type.

Anahtar Kavram

Security Control Categories and Functional Types
Tahmini Süre:1m 15s
Soru 3Soru

A systems administrator is configuring a newly deployed internal web portal to serve traffic over HTTPS using a certificate issued by the organization's Enterprise Certificate Authority (CA). Place the administrative steps in the correct chronological order required to successfully enroll and enable the TLS certificate on the web portal.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct chronological order for enrolling and enabling a TLS certificate is: 1) Generate the local key pair, 2) Construct the Certificate Signing Request (CSR) with public key and SAN, 3) Submit the CSR to the Certificate Authority (CA), 4) Import the issued X.509 certificate and intermediate trust chain onto the server, and 5) Bind the certificate to the web daemon HTTPS listener.
The correct order follows the standard PKI certificate lifecycle. The key pair must be generated on the destination server first to ensure private key protection. The public key is bundled with domain identity parameters (such as the SAN extension) into a CSR. The CSR is transmitted to the CA for signing. After the CA returns the signed X.509 leaf certificate along with intermediate CA certificates, they are imported to the server. Finally, the web service daemon is configured to bind the certificate to port 443 to accept secure incoming HTTPS connections.

Adım Adım Çözüm

1
Generate Key Pair locally
A secure private key is retained locally while the matching public key is prepared for inclusion in the request.
Security best practices demand that private keys are generated locally on the end system to prevent key exposure during transit.
2
Create Certificate Signing Request (CSR)
A CSR payload containing identity details (SAN, CN) and the public key is produced.
The CSR acts as the standardized request format that the Certificate Authority processes.
3
Submit CSR to the Certificate Authority (CA)
The CA signs the public key and identity data using its own private key, producing a valid X.509 certificate.
Only a trusted CA can vouch for the authenticity of the server's public key.
4
Import Certificate and Intermediate Chain
The server stores the signed leaf certificate and establishes the chain of trust back to the root CA.
Clients connecting to the server require both the leaf certificate and intermediate certificates to validate the signature hierarchy.
5
Bind Certificate to Port 443 HTTPS Listener
The web daemon presents the installed certificate during incoming TLS handshakes.
Binding connects the network interface daemon to the stored certificate and corresponding private key.

Anahtar Kavram

PKI Certificate Lifecycle and CSR Enrollment Workflow
Soru 4Soru

An enterprise network security team deploys a centralized RADIUS architecture to manage access to infrastructure devices. During a post-implementation audit, a security analyst notes the following behavior: when network administrators log in, the system successfully validates their multi-factor credentials. However, upon login, all authenticated administrators are granted identical, unrestricted administrative permissions across all switches and firewalls, regardless of their specific role or group membership in the directory service. Meanwhile, session start/end timestamps and data transfer metrics are accurately recorded in central logs. Which component of the AAA framework failed to be properly configured to restrict administrative privileges?

Cevabı ve açıklamayı göster

Cevap: Authorization controls enforcing role-based access limits

Cevap

Authorization controls enforcing role-based access limits
Authorization is the AAA pillar responsible for granting or denying access rights and privileges to resources once an identity is verified. In this scenario, credentials are confirmed (Authentication) and sessions are logged (Accounting), but permissions are unconstrained due to missing or misconfigured role-based authorization controls.

Adım Adım Çözüm

1
Analyze the AAA functions described in the enterprise scenario
Identity verification via multi-factor credentials succeeds (Authentication is functional). Session tracking and log metrics are recorded (Accounting is functional).
Differentiating between identity verification, permission granting, and logging is required to isolate the failure.
2
Identify the misconfiguration in permission assignment
All authenticated identities receive universal full access without evaluating specific user roles or directory attributes.
Determining permissions and enforcing principle of least privilege is the explicit responsibility of the Authorization pillar.
3
Select the missing or misconfigured AAA pillar
Authorization controls failed to enforce role-based access boundaries.
Without proper authorization policies (such as RADIUS VSAs or TACACS+ command authorization rules), authentication alone results in over-privileged access.

Anahtar Kavram

Role-based Authorization within AAA Framework
Soru 5Soru

A network engineer notices that users connecting to the enterprise Wi-Fi are successfully validating their domain credentials against a centralized RADIUS server. However, after successful login, all users—including system administrators—are placed into a restricted guest VLAN instead of being assigned their appropriate department VLANs. Which aspect of the AAA framework is failing to execute correctly in this scenario?

Cevabı ve açıklamayı göster

Cevap: Assigning dynamic network access rights and group privileges upon successful identification

Cevap

Assigning dynamic network access rights and group privileges upon successful identification
The scenario describes a successful authentication phase where the RADIUS server validates credentials. However, the system fails during the authorization phase because it does not apply role-based access rules or assign the correct network attributes (such as VLAN IDs) based on user permissions.

Adım Adım Çözüm

1
Analyze the AAA phase results in the scenario.
Domain credential validation against RADIUS succeeded, confirming authentication is working.
Authentication verifies identity, which occurred without error.
2
Identify the point of failure after login.
Users are incorrectly assigned to a restricted guest VLAN regardless of their group roles.
Determining what resources or network segments a user can access post-login is authorization.
3
Match the failed function to the correct AAA component.
The failure to grant appropriate VLAN permissions is an authorization failure.
Authorization enforces access rights based on identity and policy.

Anahtar Kavram

Distinction between Authentication (verifying identity) and Authorization (granting permissions/access)
Soru 6Soru

An automated algorithmic trading platform logs high-frequency order requests to an external compliance vault. Following a significant financial anomaly, a senior trader asserts that a series of unauthorized trades attributed to their user account were forged by a malicious internal microservice rather than initiated from their terminal. To resolve the dispute, the security audit team must provide irrefutable proof of the trader's authorship as well as guarantee that the order data was not tampered with after creation. Which of the following security mechanisms best fulfills these requirements?

Cevabı ve açıklamayı göster

Cevap: Digital signatures generated using the trader's asymmetric private key paired with a public key infrastructure timestamping service

Cevap

Digital signatures generated using the trader's asymmetric private key paired with a public key infrastructure timestamping service
Digital signatures fulfill non-repudiation because they rely on asymmetric cryptography. Only the owner possesses the private key used to sign the transaction payload, creating a unique cryptographic proof of origin. Recipients verify signature validity using the sender's public key. Timestamping further ensures proof of existence at a specific time, preventing the trader from denying trade initiation.

Adım Adım Çözüm

1
Analyze the operational security requirement in the compliance scenario
Identified the requirement for non-repudiation (proving authorship so the sender cannot deny originating the transaction) and integrity (ensuring the payload was not altered post-submission).
The trader claims an internal service forged their order, requiring cryptographic evidence that uniquely ties transaction creation to the trader.
2
Evaluate candidate cryptographic controls against non-repudiation principles
Asymmetric digital signatures uniquely bind the transaction payload to the private key owner, which cannot be forged by other services possessing only public keys or shared secrets.
Symmetric encryption and plain cryptographic hashes rely on shared keys or public hash functions, allowing any component with key access to build valid signatures and failing proof-of-origin tests.
3
Select the control combination providing both integrity and non-repudiation
Digital signatures with PKI timestamping satisfy both requirements.
The asymmetric private key guarantees non-repudiation of origin while hash-based digital signing guarantees message integrity.

Anahtar Kavram

Non-Repudiation vs Integrity in Asymmetric Cryptography
Soru 7Soru

A network administrator configures a centralized syslog server to record user login timestamps, executed command histories, and session resource usage for auditing compliance. Which core component of the AAA framework is being implemented?

Cevabı ve açıklamayı göster

Cevap: Accounting

Cevap

Accounting
Accounting is responsible for tracking user actions, monitoring session durations, and maintaining log entries of system resource consumption. This data provides accountability and essential records for security auditing.

Adım Adım Çözüm

1
Identify the primary operational activity described in the scenario
The activity involves capturing timestamps, command histories, and system resource usage into log files.
Determining the functional goal (logging activity vs granting access vs checking credentials) isolates the correct AAA pillar.
2
Map the identified activity to the AAA framework pillars
Tracking usage data and generating audit logs directly corresponds to Accounting.
Accounting measures resource usage and collects audit information for billing, capacity planning, and security investigations.

Anahtar Kavram

Authentication, Authorization, and Accounting (AAA)
Soru 8Soru

A network security administrator is evaluating access control mechanisms following an audit of an enterprise infrastructure. The current deployment utilizes RADIUS for network access control and TACACS+ for network device management. During the audit, management observed that while remote administrative login attempts are logged, the security team cannot verify which specific commands were executed by individual engineers on edge routers during maintenance sessions. Additionally, permission checks fail to evaluate individual command authorizations dynamically. Which TWO of the following architectural distinctions or protocol changes should the administrator implement to resolve these issues? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Migrate administrative router sessions to TACACS+, which decouples authentication, authorization, and accounting to support granular per-command authorization and accounting.; Implement TACACS+ command authorization profiles to evaluate each CLI command requested by an administrator against central policy before execution.

Cevap

The administrator must migrate administrative sessions to TACACS+ to separate AAA services for per-command logging and implement TACACS+ command authorization profiles to dynamically check individual CLI commands before execution.
TACACS+ is designed specifically for device administration because it separates authentication, authorization, and accounting into independent functions. This separation enables network devices to send authorization queries to the server for every individual command an administrator attempts to execute and generate distinct accounting records for each executed command. The selections recommending TACACS+ session migration and command authorization profile enforcement directly fulfill these security objectives.

Adım Adım Çözüm

1
Analyze the technical deficit described in the scenario
Identified missing granular command-level authorization and command execution accounting during administrative SSH/console sessions.
The scenario requires tracking specific executed CLI commands and controlling permission checks per command.
2
Evaluate protocol capabilities between RADIUS and TACACS+
RADIUS combines authentication and authorization and provides session-level accounting. TACACS+ separates AAA functions into distinct processes and encrypts all packet payloads.
Separating AAA allows TACACS+ to perform authorization checks for each individual command entered on a network device.
3
Select the appropriate controls to fulfill both requirements
Using TACACS+ for administrative sessions provides the required granular command accounting, while configuring command authorization profiles enforces per-command privilege checks.
These controls directly resolve the inability to track CLI command history and enforce fine-grained authorization.

Anahtar Kavram

AAA Protocol Differences (RADIUS vs. TACACS+ Granularity)
Soru 9Soru

A security analyst is investigating an incident where an attacker compromised a low-privileged service account's API key. The API gateway successfully verified the key's digital signature and validated the identity of the service account. However, due to a missing role-mapping rule on the API gateway, the request was granted access to an internal database management endpoint intended exclusively for domain administrators. Additionally, because the gateway was configured to log only initial connection handshakes rather than detailed endpoint requests, security teams cannot determine which database commands were executed. Which of the following correctly identifies the AAA pillar that failed to restrict endpoint access, and the AAA pillar whose configuration deficiency prevents auditing the executed actions?

Cevabı ve açıklamayı göster

Cevap: Authorization failed to enforce role-based access restrictions, while Accounting failed to record endpoint transaction logs.

Cevap

Authorization failed to enforce role-based access restrictions, while Accounting failed to record endpoint transaction logs.
The correct answer accurately separates the duties of the AAA framework. Authentication succeeded because the service account's API key signature was validated. Authorization failed because the gateway did not evaluate role boundaries or ACLs before granting access to the administrator endpoint. Accounting failed because the logging configuration captured only connection handshakes instead of granular transaction logs, preventing post-incident forensic analysis.

Adım Adım Çözüm

1
Analyze the credential verification phase to evaluate Authentication.
The API gateway verified the digital signature and confirmed the service account identity. Authentication functioned correctly.
Authentication is strictly responsible for verifying identity claims using credentials, certificates, or tokens.
2
Analyze the endpoint access decision phase to evaluate Authorization.
Missing role-mapping rules allowed a low-privileged account to reach an admin endpoint. Authorization failed.
Authorization determines access rights, privileges, and resource permissions once identity is established.
3
Analyze the event tracking and auditing phase to evaluate Accounting.
Failure to log specific API endpoints and commands leaves no audit trail. Accounting failed.
Accounting logs subject activity, tracking resource consumption, commands executed, and session details for non-repudiation and analysis.

Anahtar Kavram

Distinct roles of Authentication (identity verification), Authorization (permission enforcement), and Accounting (activity logging and auditing) in AAA security architecture.
Soru 10Soru

A security operations team is deploying internal code-signing certificates generated through an enterprise two-tier PKI consisting of an offline root Certificate Authority (CA) and an online intermediate issuing CA. Developers submit Certificate Signing Requests (CSRs) for binary signing. During testing on isolated target systems that already have the offline root CA certificate installed in their trusted root store, verification fails because the operating system cannot build the certification path to validate the signature. Further inspection reveals that the intermediate CA certificate was neither bundled with the signature nor pre-installed on the target machines. Which of the following is the most appropriate action to resolve this certificate chain validation failure?

Cevabı ve açıklamayı göster

Cevap: Configure the AIA (Authority Information Access) extension in issued certificates to provide a reachable URI for the intermediate CA certificate.

Cevap

Configure the AIA (Authority Information Access) extension in issued certificates to provide a reachable URI for the intermediate CA certificate.
Configuring the AIA (Authority Information Access) extension allows validating client software to fetch the missing intermediate CA certificate via HTTP or LDAP during path building. This enables the client to successfully construct and verify the full certificate chain from the end-entity code-signing certificate up to the offline root CA.

Adım Adım Çözüm

1
Identify the cause of the trust chain validation failure.
Client systems have the offline root CA trusted, but cannot build the validation path because the intermediate CA certificate is missing.
PKI certificate validation requires a complete chain of trust from the end-entity certificate up through all intermediate CAs to an installed root CA.
2
Evaluate standard PKI mechanisms for resolving missing intermediate certificates.
The Authority Information Access (AIA) extension specifies pointers (URIs) where clients can dynamically retrieve intermediate CA certificates during path building.
Including the AIA extension enables automated certificate discovery and path construction without manual distribution of intermediate certificates to all endpoints.
3
Select the proper administrative resolution.
Configuring the AIA extension ensures clients can fetch the intermediate certificate and complete path building successfully.
This maintains the multi-tier hierarchy and offline status of the root CA while ensuring seamless signature validation.

Anahtar Kavram

Public Key Infrastructure (PKI) Certificate Chain Building and Authority Information Access (AIA)
Tahmini Süre:2m 0s
Soru 11Soru

An organization is categorizing its security controls based on CompTIA Security+ implementation categories (Technical, Managerial, Operational, Physical) and functional types (Preventive, Deterrent, Detective, Corrective, Compensating, Directive). Match each implemented security control on the left with its correct dual-classification on the right.

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

Öğeler

Restoring system operations from air-gapped immutable backups following a ransomware incident
Posting high-visibility warning signs along a perimeter fence stating that unauthorized entry triggers prosecution
Publishing an enterprise-wide security governance document mandating acceptable asset usage practices
Deploying passive Network Intrusion Detection System (NIDS) sensors to monitor core traffic for anomalous patterns

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Restoring backups matches Technical category and Corrective type; warning signs match Physical category and Deterrent type; security policy documentation matches Managerial category and Directive type; passive NIDS sensors match Technical category and Detective type.
Each mechanism aligns directly with its primary implementation axis and operational goal: system restoration via backups is Technical and Corrective; physical signage dissuading entry is Physical and Deterrent; administrative usage policies are Managerial and Directive; and passive network intrusion monitoring is Technical and Detective.

Adım Adım Çözüm

1
Analyze each security control's implementation method to assign the category (Technical, Managerial, Operational, or Physical).
Backups and NIDS are Technical (systems/software); warning signs are Physical (facility fixtures); security policies are Managerial (administrative governance).
CompTIA Security+ defines categories based on how a mechanism is constructed and deployed.
2
Evaluate the functional goal of each security control within the incident timeline (Preventive, Deterrent, Detective, Corrective, Compensating, or Directive).
Backups restore lost state (Corrective); signs warn off intruders (Deterrent); policies mandate rules (Directive); NIDS identifies anomalies (Detective).
Functional types reflect what the control accomplishes when mitigating security risks.
3
Pair each security mechanism with its corresponding category and functional type pair.
All four pairs matched accurately without ambiguity.
Dual-axis classification evaluates implementation method alongside security goal.

Anahtar Kavram

Dual-axis security control classification under CompTIA Security+ SY0-701.
Soru 12Soru

A network administrator is establishing PKI certificate management processes and automated revocation checks for a cluster of internal web applications. To ensure optimal security during certificate issuance and minimize handshake latency during revocation checking, which of the following implementation steps should the administrator select? (Select TWO).

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

Cevabı ve açıklamayı göster

Cevap: Generate the private key locally on the target web server when creating the Certificate Signing Request (CSR) before submitting it to the Certificate Authority.; Configure OCSP stapling on the web servers so that cached, digitally signed CA revocation responses are delivered directly to client browsers during the TLS handshake.

Cevap

The correct implementation steps are local private key generation during CSR creation and configuring OCSP stapling on web servers.
Generating the private key locally when creating a CSR ensures the private key is never exposed across the network. Enabling OCSP stapling allows the web server to append signed revocation proof directly during the TLS handshake, reducing latency and avoiding client connection delays.

Adım Adım Çözüm

1
Analyze certificate request lifecycle security requirements
Confirm that private keys must be generated locally on the requestor endpoint so that the key is never transferred across the network.
Maintaining private key isolation on the endpoint prevents exposure and maintains the integrity of asymmetric key pairs.
2
Evaluate revocation checking optimization methods
Identify OCSP stapling as the mechanism where web servers periodically fetch and staple timestamped, signed OCSP responses to TLS handshakes.
OCSP stapling avoids third-party OCSP responder queries by clients, eliminating external lookup latency and bandwidth overhead.

Anahtar Kavram

PKI Certificate Request Flow and OCSP Stapling Revocation Verification
Soru 13Soru

Match each core Zero Trust Architecture (ZTA) control plane component with its primary operational responsibility in accordance with NIST SP 800-207 standards.

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

Öğeler

Policy Engine (PE)
Policy Administrator (PA)
Policy Enforcement Point (PEP)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Policy Engine pairs with evaluating access requests and making decision choices; Policy Administrator pairs with issuing control commands to manage sessions; Policy Enforcement Point pairs with gating and monitoring active connections in the data path.
Each Zero Trust Architecture component fulfills a distinct logical role specified in NIST SP 800-207: the Policy Engine acts as the decision maker, the Policy Administrator serves as the controller executing control plane commands, and the Policy Enforcement Point directly controls connection flows in the data plane.

Adım Adım Çözüm

1
Identify the primary function of the Policy Engine.
Recognize that the Policy Engine is responsible for the trust decision logic.
It processes subject, resource, and environment attributes against security rules to evaluate access authorization.
2
Identify the primary function of the Policy Administrator.
Recognize that the Policy Administrator translates policy decisions into control signals.
It instructs the Policy Enforcement Point to open or close the specific session path.
3
Identify the primary function of the Policy Enforcement Point.
Recognize that the Policy Enforcement Point sits on the data plane.
It directly intercepts, enables, monitors, and terminates network connections between subjects and targets.

Anahtar Kavram

Zero Trust Architecture Control and Data Plane Components
Soru 14Soru

A security operations team wants to identify unauthorized credential harvesting and post-exploitation lateral movement within a hybrid cloud enterprise network. To achieve this without altering production network routing or risking asset compromise, the team injects synthetic cloud API keys and decoy Kerberos ticket-granting service (TGS) requests into the LSASS memory space of critical endpoints. When an attacker attempts to extract these fake credentials and present them to a decoy authentication service, an alert is triggered immediately. Which of the following deception and disruption technologies did the organization deploy?

Cevabı ve açıklamayı göster

Cevap: Honeytokens acting as breadcrumbs

Cevap

Honeytokens acting as breadcrumbs
The deployment of synthetic API keys and decoy Kerberos credentials directly into endpoint memory represents the use of honeytokens configured as breadcrumbs. Honeytokens are deceptive data items or fake credentials that trigger alerts upon unauthorized use, while breadcrumbs are host-based artifacts placed to entice attackers toward decoy resources.

Adım Adım Çözüm

1
Analyze the technical requirements of the scenario.
The organization needs to detect post-exploitation credential harvesting and lateral movement from host memory without impacting production routing.
Traditional perimeter defenses often miss lateral movement when legitimate tools or stolen memory credentials are used.
2
Evaluate the deployed deceptive elements.
The deployed artifacts are fake credentials (synthetic API keys and decoy Kerberos TGS tickets) placed on endpoints to guide adversaries into decoy authentication traps.
Fake credentials or data items designed to trigger alerts when accessed are classified as honeytokens, and when strategically left on host systems to lure attackers, they function as breadcrumbs.
3
Differentiate honeytokens/breadcrumbs from network honeynets, traditional IPS controls, and honeyfiles.
Decoy host memory credentials map precisely to honeytokens serving as breadcrumbs rather than network-level honeynets, DNS sinkholes, or file-based honeyfiles.
Honeytokens target credential usage and memory inspection, while honeyfiles target file system operations and honeynets simulate entire network segments.

Anahtar Kavram

Deception Technologies: Honeytokens and Breadcrumbs
Soru 15Soru

A systems administrator is configuring a secure remote management channel for server administration over an untrusted network. The security policy mandates perfect forward secrecy so that compromising the server's long-term private key in the future will not allow an attacker to decrypt previously recorded session traffic. Which cryptographic key exchange mechanism should the administrator implement to satisfy this requirement?

Cevabı ve açıklamayı göster

Cevap: Ephemeral Diffie-Hellman key exchange

Cevap

Ephemeral Diffie-Hellman key exchange should be selected because ephemeral keys provide perfect forward secrecy for encrypted sessions.
Ephemeral Diffie-Hellman key exchange satisfies perfect forward secrecy requirements because a unique, temporary key pair is generated for each communication session. Once the session ends, the temporary keys are discarded. An attacker who compromises the server's long-term private key at a later date cannot derive previous session keys or decrypt captured historical traffic.

Adım Adım Çözüm

1
Identify the primary requirement specified in the scenario
The requirement is perfect forward secrecy (PFS) for remote management sessions over an untrusted network.
The system must protect historical session logs from decryption even if long-term server private keys are compromised.
2
Evaluate key exchange mechanisms against the requirement
Ephemeral key exchanges (such as ECDHE or DHE) generate temporary, disposable keys per session rather than deriving session keys from long-term asymmetric keys.
Because temporary session keys are not stored and cannot be derived from long-term keys, forward secrecy is maintained.
3
Select the option that implements ephemeral key exchange
Ephemeral Diffie-Hellman key exchange correctly satisfies the security requirement.
It ensures that compromising long-term keys does not compromise past communication sessions.

Anahtar Kavram

Perfect Forward Secrecy via Ephemeral Diffie-Hellman
Soru 16Soru

A security technician is troubleshooting a user access issue on a corporate document platform. The user successfully validates their password and multi-factor authentication prompt at login. However, when attempting to open shared department folders, the platform denies access with a 'Privilege Insufficient' error. System logs confirm that the identity provider successfully verified who the user is, but failed to evaluate or grant access permissions to the requested resources. Which component of the AAA framework is failing to execute as intended?

Cevabı ve açıklamayı göster

Cevap: Authorization

Cevap

Authorization is the failing component because identity verification succeeded, but resource access rights were not granted.
Authorization is responsible for determining whether an authenticated subject has permission to access a specific object or resource. In this scenario, the user successfully proved their identity (authentication), but the system failed to grant or verify their access permissions for the shared folders.

Adım Adım Çözüm

1
Analyze the problem statement for authentication activity.
The user successfully validated credentials and MFA, confirming that the Authentication step succeeded.
Authentication verifies identity.
2
Analyze the access failure.
The system blocked access due to missing permissions ('Privilege Insufficient').
Determining what actions an authenticated user can perform on specific resources is the function of Authorization.
3
Identify the failing AAA pillar.
Authorization failed because permission evaluation/granting did not take place properly.
Authorization explicitly governs rights and permission assignment in AAA.

Anahtar Kavram

Authentication vs. Authorization vs. Accounting (AAA)
Soru 17Soru

An organization plans to deprecate legacy cryptographic protocols across all internal application gateways during a scheduled maintenance window. Following the change execution, several mission-critical legacy internal applications lose connection to the centralized authentication service, causing widespread business disruption. Investigation reveals that while the protocol deprecation was approved by the Change Advisory Board (CAB), the technical change request did not evaluate application-level dependency on legacy protocol suites. Which of the following change management practices was omitted prior to submission?

Cevabı ve açıklamayı göster

Cevap: Performing a security impact assessment and system dependency analysis to identify technical prerequisites and legacy integration requirements.

Cevap

Performing a security impact assessment and system dependency analysis to identify technical prerequisites and legacy integration requirements.
The correct answer emphasizes performing a security impact assessment and dependency analysis. Before any major infrastructure modification is presented to a Change Advisory Board (CAB), administrators must evaluate how security configuration changes affect existing applications and inter-service dependencies. Identifying these legacy requirements ahead of time ensures necessary adjustments or exceptions are addressed before deployment.

Adım Adım Çözüm

1
Analyze the change management failure scenario.
Identified that cryptographic protocol removal caused cascading authentication failures due to unmapped dependencies.
Changes to security settings must be thoroughly evaluated for technical interdependencies before implementation.
2
Evaluate the required pre-implementation change control phase.
A thorough security impact assessment and dependency mapping would have highlighted legacy application reliance on the protocol.
Change management workflows require assessing operational and security impacts to ensure backout plans and compatibility checks are established.

Anahtar Kavram

Security Impact Assessment and Dependency Analysis in Change Management
Soru 18Soru

A cloud-native software provider operates a microservices workload where internal APIs communicate across multiple environments. A threat actor successfully steals active bearer tokens from a developer workstation located on the internal office LAN. When the attacker uses these stolen tokens to invoke downstream financial data microservices from inside the corporate network, access is denied due to an anomalous device posture score and unverified request velocity. Which core Zero Trust Architecture principle directly prevented this lateral movement despite the presentation of valid authentication credentials from an internal source?

Cevabı ve açıklamayı göster

Cevap: Continuous contextual authorization that dynamically evaluates transaction risk and endpoint health for every microservice request

Cevap

Continuous contextual authorization that dynamically evaluates transaction risk and endpoint health for every microservice request.
The correct answer highlights continuous contextual authorization. Under Zero Trust Architecture (ZTA), trust is never implicitly granted based on network location or initial login success. Every access request is individually evaluated using real-time signals—such as device security posture, user behavior anomalies, and request velocity—before authorization is granted by the Policy Enforcement Point (PEP).

Adım Adım Çözüm

1
Analyze the threat scenario and failure point for the attacker.
The attacker possesses valid authentication tokens and operates from inside the internal corporate network, yet the request is blocked based on contextual anomaly and device health.
This isolates the security mechanism from static perimeter defense or simple token validity check.
2
Map the defensive control to Zero Trust tenets.
Zero Trust assumes breach and requires continuous verification—evaluating every request individually using real-time attributes like user context, device health, location, and request anomalies.
Authenticating once at login or relying on internal network location does not grant persistent access across microservice workloads.
3
Select the option that reflects real-time continuous evaluation.
The option specifying continuous contextual authorization accurately describes the mechanism enforcing policy per request.
It addresses why stolen valid credentials fail when contextual parameters fail policy inspection.

Anahtar Kavram

Continuous Verification and Contextual Authorization in Zero Trust Architecture
Soru 19Soru

Match each Zero Trust Architecture (ZTA) logical component defined in NIST SP 800-207 to its primary operational responsibility.

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

Öğeler

Policy Engine (PE)
Policy Administrator (PA)
Policy Enforcement Point (PEP)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The Policy Engine is responsible for evaluation and authorization decisions; the Policy Administrator handles control plane management and session credential signaling; the Policy Enforcement Point actively enforces access controls directly within the data plane.
According to NIST SP 800-207 Zero Trust Architecture, the Policy Engine handles the decision logic, the Policy Administrator handles control plane orchestrations and session keys, and the Policy Enforcement Point performs data plane enforcement directly on connections.

Adım Adım Çözüm

1
Identify the core decision-making entity within the control plane.
The Policy Engine evaluates context, identity, and posture against trust rules to grant or deny access.
Zero Trust separates policy decision-making from policy enforcement mechanisms.
2
Determine which component translates policy decisions into control plane commands.
The Policy Administrator receives the decision from the Policy Engine and communicates with enforcement points to initiate or terminate communication channels.
The Policy Administrator serves as the controller orchestrating session setup and credential issuance.
3
Identify the data plane component interacting directly with network connections.
The Policy Enforcement Point monitors and filters data traffic, enabling or tearing down access sessions.
Enforcement must happen directly at the boundary of the requested resource or workload.

Anahtar Kavram

Logical Architecture of Zero Trust (NIST SP 800-207 Control and Data Planes)
Soru 20Soru

An enterprise DevOps team implements a security policy requiring all software developers to digitally sign Git commits using their individual GPG private keys prior to merging code into the production repository. The central repository server automatically validates each signature against the developer's registered public key. Which of the following security objectives are directly achieved by enforcing this digital signature mechanism? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Non-repudiation, by cryptographically binding the author's identity to the commit so the developer cannot deny authoring the code.; Integrity, by ensuring the commit contents have not been altered or tampered with since the signature was applied.

Cevap

The correct options are non-repudiation (binding author identity to code commits via private keys) and integrity (ensuring code has not been tampered with post-signing).
Digital signatures leverage asymmetric cryptography (signing with a private key and verifying with a public key). This mechanism provides non-repudiation because the signature uniquely identifies the key holder who submitted the code, and integrity because any modification to the source code invalidates the cryptographic signature.

Adım Adım Çözüm

1
Analyze the technical control described in the scenario.
The scenario describes using asymmetric GPG keys to sign Git commits, where a private key creates the signature and a public key verifies it.
Understanding the underlying cryptographic mechanism determines which security goals are fulfilled.
2
Evaluate how asymmetric digital signatures map to CIA triad pillars and non-repudiation.
Digital signatures provide integrity (detecting data modification via signed hash) and non-repudiation (proving identity via unshared private key).
Because only the private key owner can generate the signature, the signer cannot claim another party authored the code (non-repudiation). Because a hash of the content is signed, changes alter the hash and fail validation (integrity).
3
Evaluate and eliminate incorrect security objectives.
Confidentiality is not provided because signatures do not encrypt the underlying source code. Availability is not provided because signing does not mitigate server downtime or denial-of-service attacks.
Confidentiality requires data encryption, while availability requires redundant architecture and DDoS mitigations.

Anahtar Kavram

Digital signatures built on asymmetric cryptography provide both Integrity and Non-Repudiation, but do not provide Confidentiality or Availability.
Sayfa 1 / 14Sonraki