Question 910
A control review focuses on certificate revocation status. Which explanation best matches its mechanics?
- Public-key cryptography can use a recipient's public key to establish confidentiality while the private key stays secret.
- Envelope encryption encrypts bulk content with data keys and wraps those keys under a separate managed key.
- Revocation lets relying parties learn that an otherwise unexpired certificate should no longer be trusted.
- Certificate validation relies on a chain of appropriate signatures, trust anchors, usage constraints, and identity matching.
Explanation
Correct Answer
C:A certificate's private key is compromised well before its scheduled expiration date; that situation illustrates the actual operating behavior under review. Its practical safeguard is to revoke the affected certificate, replace keys, and configure appropriate status distribution, with confirmation when status checks identify the compromised certificate as revoked and accept its valid replacement.
Incorrect Answers
A:A sender needs to protect a short secret for a recipient without first sharing a symmetric key; those details characterize asymmetric key roles and would call for validate recipient public keys and protect the associated private key from unauthorized use, rather than explaining certificate revocation status.
B:A storage platform encrypts each object with a short-lived data key protected by a central master key; those details characterize envelope encryption and would call for use per-object or per-context data keys and limit master-key unwrap permissions, rather than explaining certificate revocation status.
D:An HTTPS endpoint presents a leaf certificate but no valid path to a trusted certificate authority; those details characterize certificate chain trust and would call for install the correct intermediate certificates and require full client trust validation, rather than explaining certificate revocation status.
Question 911
A control review focuses on serverless least privilege. Which explanation best matches its mechanics?
- Stateless cloud network ACLs require explicit allowance for both request and response directions.
- Serverless code still runs with an identity whose permissions determine its possible cloud-side actions.
- Cloud workload firewalls or security groups constrain permitted instance traffic and may track connection state.
- Cloud service providers secure assigned infrastructure layers while customers remain accountable for their configurations and data.
- Cloud control-plane audit trails capture identity and API activity when correctly enabled and retained.
Explanation
Correct Answer
B:An event-triggered cloud function can invoke unrelated administrative APIs using its execution role; that situation illustrates the actual operating behavior under review. Its practical safeguard is to grant the function only event-processing actions and scope them to exact resources, with confirmation when role-policy tests show unrelated administrative API operations denied to the function identity.
Incorrect Answers
A:A subnet-level stateless rule permits inbound application packets but blocks required response traffic; those details characterize cloud network acl behavior and would call for review directional subnet rules and required response ports as a complete network flow, rather than explaining serverless least privilege.
C:A virtual machine accepts administrative traffic from every internet address because of an overly broad inbound rule; those details characterize cloud network security groups and would call for limit administrative ingress to approved bastion or management source ranges, rather than explaining serverless least privilege.
D:A hosted database customer assumes the provider also determines application user permissions and data retention; those details characterize cloud shared responsibility and would call for document the service-model responsibility split and enforce customer-side identity and data controls, rather than explaining serverless least privilege.
E:A privileged cloud policy change is discovered but the team cannot identify who made the API request; those details characterize cloud audit logging and would call for enable organization-wide control-plane logs in protected centralized storage, rather than explaining serverless least privilege.
Question 912
A planned improvement must address the following: An administrative API lists internal user identifiers through an endpoint open to all clients. Which control best targets that requirement?
- Restrict RPC management interfaces to trusted subnets and authorized authenticated clients.
- Require authorization on collection endpoints and restrict fields returned to each role.
- Restrict exports by trusted clients and enforce appropriate identity mapping and access permissions.
- Disable public anonymous access unless the published data is expressly intended for unrestricted release.
Explanation
Correct Answer
B:Excessive API enumeration arises when list endpoints lack authorization or safe pagination and filtering; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that tests with an unprivileged token cannot list restricted identifiers or fields.
Incorrect Answers
A:RPC endpoint information can reveal reachable management interfaces and service dependencies; the proposed safeguard addresses a case where an endpoint lists remotely exposed interface identifiers and service bindings to unknown clients, rather than the public API directory listing finding described here.
C:NFS export configurations can expose mountable file systems and depend on host and user identity controls; the proposed safeguard addresses a case where a storage server discloses exported file systems to a remote system outside its application tier, rather than the public API directory listing finding described here.
D:Anonymous FTP can publish files and names without identity verification or transport encryption; the proposed safeguard addresses a case where an old file-transfer service exposes a directory listing to a user without authentication, rather than the public API directory listing finding described here.
Question 913
A trainee confuses several related concepts with website metadata leakage. Which explanation resolves that confusion?
- Office and PDF metadata can expose organizational identifiers even when the document body is harmless.
- PTR records provide reverse address-to-name mapping, which may not mirror forward DNS perfectly.
- Public professional profiles can reveal personnel relationships and likely administrative roles without system access.
- DKIM binds selected message headers and body content to a signing domain using a published public key.
Explanation
Correct Answer
A:A publicly downloadable document reveals its author name, software version, and internal path in properties; that situation illustrates the actual operating behavior under review. Its practical safeguard is to strip unnecessary document properties during the publishing workflow, with confirmation when published files inspected after export contain no internal paths, usernames, or sensitive production metadata.
Incorrect Answers
B:A network analyst wants the published hostname associated with an IP address rather than its forward address; those details characterize reverse DNS mapping and would call for review PTR naming for unintended system details and maintain accurate operational records, rather than explaining website metadata leakage.
C:A tester maps employee job titles and technology responsibilities from openly published profiles; those details characterize social profile correlation and would call for train staff on oversharing and limit unnecessary public details about privileged responsibilities, rather than explaining website metadata leakage.
D:An outbound message carries a domain-associated cryptographic signature that receiving mail servers can verify; those details characterize DKIM signature verification and would call for rotate protected signing keys and publish the matching selector record in DNS, rather than explaining website metadata leakage.
Question 914
A remediation ticket for hash-based integrity needs technical proof before closure. Which test result fits?
- Signature tests detect alteration and encrypted-message tests prevent unauthorized reading.
- Benchmark records confirm configured hash parameters and successful authentication remains operationally acceptable.
- Database samples show different salts and derived hashes for equal controlled test passwords.
- Recomputed digests match documented originals and differ when controlled content changes.
Explanation
Correct Answer
D:A cryptographic hash creates a fixed-length digest useful for checking content integrity, not encrypting content; the outcome tests this precise property in the production control. It relates to the original observation that a forensic copy must be compared with its original to detect byte-level changes.
Incorrect Answers
A:Email signatures provide authenticity and integrity; confidentiality requires separate encryption of content; that evidence is relevant when a recipient must verify a message's sender integrity while recognizing that signatures do not inherently hide message text, but does not establish closure of the hash-based integrity exposure.
B:Memory-hard password KDFs raise the RAM and computation cost of each guessing attempt; that evidence is relevant when an identity service must make large-scale offline password guessing expensive on parallel hardware, but does not establish closure of the hash-based integrity exposure.
C:A unique random salt makes identical passwords yield different password-hash outputs under the same KDF; that evidence is relevant when two users have identical passwords but their stored password hashes must not reveal that equality directly, but does not establish closure of the hash-based integrity exposure.
Question 915
In a controlled review, analysts encounter this situation: A service receives a disproportionately large volume of unsolicited replies from unrelated public servers. Select the best matching concept.
- Application-layer request flood
- Resource exhaustion through connection state
- Reflection amplification
- Volumetric DDoS
Explanation
Correct Answer
C:Reflection abuses third-party responders and source-address spoofing; amplification increases response traffic relative to requests; that mechanism makes this classification more precise than the neighboring terms. The protective follow-up is to filter spoofed-source traffic and work with upstream protection against unwanted reflected replies, verified when edge captures show reflected packets mitigated and anti-spoofing controls prevent forged outbound origins.
Incorrect Answers
A:Layer-seven denial-of-service targets application processing resources rather than just raw link bandwidth; this different classification would fit when a web service exhausts worker capacity under many costly but syntactically valid application requests, not the evidence pointing to reflection amplification in the question.
B:State-exhaustion attacks consume finite connection resources before useful application work begins; this different classification would fit when a server accumulates large numbers of unfinished connection attempts and runs out of state-table capacity, not the evidence pointing to reflection amplification in the question.
D:Volumetric denial-of-service overwhelms network bandwidth before ordinary application controls can respond; this different classification would fit when an internet circuit saturates with traffic from many unrelated networks while the web application remains healthy locally, not the evidence pointing to reflection amplification in the question.
Question 916
An authorized security review records the following: A responder finds an HTTP-speaking service listening on an unexpected numeric port. Which concept most accurately classifies the observation?
- UDP response ambiguity
- TCP reset interpretation
- Exposure from shadow services
- Port-to-service mismatch
- Filtered TCP port
Explanation
Correct Answer
D:Port numbers are conventions; application-layer content and process ownership establish actual service identity; that mechanism makes this classification more precise than the neighboring terms. The protective follow-up is to verify listener processes and application protocols rather than assigning services by port number alone, verified when host socket inventory and an approved protocol exchange identify the true process and service.
Incorrect Answers
A:UDP lacks a connection handshake; silence alone does not prove whether an application is listening; this different classification would fit when a UDP service probe returns no payload and no reachable error indication, not the evidence pointing to port-to-service mismatch in the question.
B:A reset typically signals a rejected or nonexistent TCP connection, which differs from silent filtering; this different classification would fit when a probe receives an immediate RST from a reachable address rather than a service welcome banner, not the evidence pointing to port-to-service mismatch in the question.
C:Uninventoried listeners can expose control planes without ordinary maintenance or review; this different classification would fit when a listening management interface appears on a newly provisioned host but is absent from the service catalog, not the evidence pointing to port-to-service mismatch in the question.
E:Filtering or packet loss can prevent a conclusive TCP port-state observation from a remote position; this different classification would fit when a probe to a specific port receives no response while other ports on the same host reply, not the evidence pointing to port-to-service mismatch in the question.
Question 917
A client-approved assessment includes this finding: An old file-transfer service exposes a directory listing to a user without authentication. What is the most precise security term for it?
- NFS export listing
- SMB share exposure
- Anonymous LDAP bind
- Anonymous FTP listing
Explanation
Correct Answer
D:Anonymous FTP can publish files and names without identity verification or transport encryption; that mechanism makes this classification more precise than the neighboring terms. The protective follow-up is to disable public anonymous access unless the published data is expressly intended for unrestricted release, verified when unauthenticated listing requests cannot enumerate private directories on the file-transfer service.
Incorrect Answers
A:NFS export configurations can expose mountable file systems and depend on host and user identity controls; this different classification would fit when a storage server discloses exported file systems to a remote system outside its application tier, not the evidence pointing to anonymous FTP listing in the question.
B:SMB share enumeration reveals network resource names and sometimes access permissions before file access is attempted; this different classification would fit when a file server lists sensitive shared folders to users who do not need to know those names, not the evidence pointing to anonymous FTP listing in the question.
C:LDAP directory reads can disclose identity structure when anonymous search rights are too broad; this different classification would fit when a directory service returns user and group details to an unauthenticated client connection, not the evidence pointing to anonymous FTP listing in the question.
Question 918
A responder documents this evidence: Two users have identical passwords but their stored password hashes must not reveal that equality directly. Which concept is being demonstrated?
- Asymmetric key roles
- Password salt uniqueness
- Symmetric confidentiality
- Hash-based integrity
Explanation
Correct Answer
B:A unique random salt makes identical passwords yield different password-hash outputs under the same KDF; that mechanism makes this classification more precise than the neighboring terms. The protective follow-up is to generate independent salts per password and store them alongside slow password hashes, verified when database samples show different salts and derived hashes for equal controlled test passwords.
Incorrect Answers
A:Public-key cryptography can use a recipient's public key to establish confidentiality while the private key stays secret; this different classification would fit when a sender needs to protect a short secret for a recipient without first sharing a symmetric key, not the evidence pointing to password salt uniqueness in the question.
C:Symmetric algorithms use a shared secret for encryption and decryption and are efficient for bulk data; this different classification would fit when a large backup needs efficient encryption and decryption with the same protected secret key, not the evidence pointing to password salt uniqueness in the question.
D:A cryptographic hash creates a fixed-length digest useful for checking content integrity, not encrypting content; this different classification would fit when a forensic copy must be compared with its original to detect byte-level changes, not the evidence pointing to password salt uniqueness in the question.
Question 919
Which mechanism should a defender associate with cloud audit logging?
- Broad cloud roles amplify a compromised workload's capabilities outside its necessary operations.
- Cloud control-plane audit trails capture identity and API activity when correctly enabled and retained.
- Serverless code still runs with an identity whose permissions determine its possible cloud-side actions.
- Managed key services help separate protected key access, rotation policy, and audit from application source code.
Explanation
Correct Answer
B:A privileged cloud policy change is discovered but the team cannot identify who made the API request; that situation illustrates the actual operating behavior under review. Its practical safeguard is to enable organization-wide control-plane logs in protected centralized storage, with confirmation when a test policy change produces a timestamped log with principal, action, resource, and outcome.
Incorrect Answers
A:A serverless function can administer all storage resources even though it reads one designated object; those details characterize cloud iam overprivilege and would call for attach narrow resource-scoped actions to the function's execution identity, rather than explaining cloud audit logging.
C:An event-triggered cloud function can invoke unrelated administrative APIs using its execution role; those details characterize serverless least privilege and would call for grant the function only event-processing actions and scope them to exact resources, rather than explaining cloud audit logging.
D:Application data is encrypted but the same long-lived encryption key is hardcoded into its source repository; those details characterize cloud key management and would call for use a managed key service with limited decrypt grants and remove exposed embedded keys, rather than explaining cloud audit logging.
Question 920
The security owner reviews this situation: Multiple smart sensors share an unchanged default administrative password across an entire facility. What is the most suitable targeted safeguard?
- Remove default access paths and restrict management UI reachability to authorized maintenance stations.
- Inventory firmware versions and establish supported staged updates with rollback planning.
- Require cryptographically verified updates and a secure boot chain where supported.
- Use unique per-device credentials or managed identities and disable unused default accounts.
Explanation
Correct Answer
D:Factory credentials create predictable management access if they remain active after device commissioning; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that inventory tests show factory logins rejected and approved maintenance identities individually tracked.
Incorrect Answers
A:Embedded management interfaces may retain obsolete defaults and limited authentication controls for years; the proposed safeguard addresses a case where a connected controller exposes a vendor maintenance page with unchanged factory settings over the plant network, rather than the IoT factory credentials finding described here.
B:Unmanaged update processes leave persistent known weaknesses in long-lived embedded deployments; the proposed safeguard addresses a case where deployed devices receive security fixes inconsistently because no operator owns their update policy, rather than the IoT factory credentials finding described here.
C:Unsigned update paths permit modified firmware to be accepted as if it were trusted vendor software; the proposed safeguard addresses a case where a gateway installs downloaded firmware without checking that it came from an approved signer, rather than the IoT factory credentials finding described here.