Question 600
A finding concerns business logic abuse. Select the explanation that captures how this issue or control works.
- State-changing form endpoints are vulnerable when ambient cookies alone authorize cross-origin requests.
- Traversal occurs when user-controlled paths escape the allowed base directory after unsafe normalization.
- Function authorization requires server-side role checks independent of hidden menus or client display logic.
- Logic flaws exploit allowed operations in an unintended sequence or frequency, beyond ordinary injection filters.
Explanation
Correct Answer
D:A discount checkout allows repeated redemption of a one-time credit without breaking input validation; that situation illustrates the actual operating behavior under review. Its practical safeguard is to enforce transactional limits and invariants on the server for credit redemption and purchase flows, with confirmation when repeated-redemption test cases cannot exceed the intended one-credit business rule.
Incorrect Answers
A:A browser submits a password-change form while the user is logged in but without evidence of intended action; those details characterize cross-site request forgery in forms and would call for verify anti-CSRF tokens and origin context for browser-based state-changing operations, rather than explaining business logic abuse.
B:A download endpoint accepts a filename with parent-directory components and reads outside its intended folder; those details characterize path traversal protection and would call for resolve and constrain paths to an approved root and use object identifiers instead of raw filesystem paths, rather than explaining business logic abuse.
C:A regular user reaches an administrator-only action by directly calling its API route; those details characterize function-level authorization flaw and would call for check authorization on each privileged operation and deny unentitled roles server-side, rather than explaining business logic abuse.
Question 601
A remediation ticket for sms phishing needs technical proof before closure. Which test result fits?
- Physical access observations show every entrant presents an authorized credential or escort approval.
- Call handling records show staff refuse unsolicited code requests and use established support contacts.
- Training results show test recipients avoid entering credentials into unsolicited SMS links.
- Test events show unsolicited approval requests are rejected and reported through the security channel.
Explanation
Correct Answer
C:Smishing delivers fraudulent instructions through text messages rather than email or phone calls; the outcome tests this precise property in the production control. It relates to the original observation that a text message uses a package-delivery pretext to send a user to an unfamiliar sign-in site.
Incorrect Answers
A:Tailgating exploits courtesy or distraction to cross physical security boundaries without individual authorization; that evidence is relevant when an unbadged visitor follows a legitimate employee through a controlled door without presenting credentials, but does not establish closure of the sms phishing exposure.
B:Vishing exploits voice conversations to elicit secrets or persuade users to take unsafe actions; that evidence is relevant when a caller posing as technical support asks an employee to read a one-time login code aloud, but does not establish closure of the sms phishing exposure.
D:Social pressure can convert an MFA approval into user-assisted account takeover despite a separate factor; that evidence is relevant when an attacker instructs a user to approve an unsolicited authenticator prompt as part of a supposed help-desk repair, but does not establish closure of the sms phishing exposure.
Question 602
An approved test produces this finding: A mail security report shows messages rejected when visible sender identity fails domain alignment checks. Which protective action most directly addresses it?
- Rotate protected signing keys and publish the matching selector record in DNS.
- Validate the trusted header chain and sender authentication rather than trusting the visible From display name.
- Keep published mail-routing records accurate and retire obsolete mail exchangers.
- Coordinate with the partner to remove excessive disclosures and limit shared identifiers.
- Configure DMARC reporting and an enforcement policy appropriate to the domain's readiness.
Explanation
Correct Answer
E:DMARC evaluates alignment with SPF or DKIM and lets the domain owner publish reporting and handling policy; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that aggregate reports show legitimate aligned traffic and policy handling of spoofed sender identities.
Incorrect Answers
A:DKIM binds selected message headers and body content to a signing domain using a published public key; the proposed safeguard addresses a case where an outbound message carries a domain-associated cryptographic signature that receiving mail servers can verify, rather than the DMARC email alignment finding described here.
B:Received headers, authentication results, and server traces can reveal message path and origin clues; the proposed safeguard addresses a case where an investigator reads the received-hop chain to distinguish real mail transit from a forged display name, rather than the DMARC email alignment finding described here.
C:MX records designate inbound mail exchanges and their relative delivery priorities; the proposed safeguard addresses a case where a mail delivery investigation needs to identify which hosts accept messages for the organization's domain, rather than the DMARC email alignment finding described here.
D:Supply-chain footprints include information published by service providers outside the main organization's domain; the proposed safeguard addresses a case where a public partner portal lists customer organization names and private service references, rather than the DMARC email alignment finding described here.
Question 603
The assessment lead requests a precise definition of MQTT broker authorization. Which technical interpretation fits?
- PLC control interfaces affect physical processes and must be shielded from unauthorized enterprise traffic.
- Embedded management interfaces may retain obsolete defaults and limited authentication controls for years.
- An industrial DMZ mediates data exchange while reducing direct enterprise-to-control-system reachability.
- MQTT publish and subscribe access requires topic-scoped authentication and authorization controls.
Explanation
Correct Answer
D:A telemetry client can subscribe to another tenant's private topics on a shared message broker; that situation illustrates the actual operating behavior under review. Its practical safeguard is to use authenticated clients with topic-level publish and subscribe permissions, with confirmation when broker tests reject cross-tenant topic access while authorized telemetry delivery remains intact.
Incorrect Answers
A:A programmable logic controller accepts management connections from the office guest network; those details characterize PLC control network exposure and would call for segment control networks and restrict engineering access through monitored approved jump paths, rather than explaining MQTT broker authorization.
B:A connected controller exposes a vendor maintenance page with unchanged factory settings over the plant network; those details characterize embedded web ui hardening and would call for remove default access paths and restrict management UI reachability to authorized maintenance stations, rather than explaining MQTT broker authorization.
C:A historian sends process data to enterprise reporting systems through unrestricted two-way connections; those details characterize industrial dmz separation and would call for introduce controlled intermediary services and restrict cross-zone flows to documented purposes, rather than explaining MQTT broker authorization.
Question 604
Which audit observation best verifies a corrective measure covering object-level authorization flaw?
- API inspection confirms regular users receive no hidden privileged properties in JSON responses.
- Cross-account tests cannot access invoices belonging to a different customer even with known identifiers.
- An ordinary user's token cannot invoke administrative API functions through direct requests.
- Authorization requests with unregistered redirects fail before codes are returned to those destinations.
Explanation
Correct Answer
B:Object-level authorization fails when the server trusts a client-chosen identifier without checking ownership; the outcome tests this precise property in the production control. It relates to the original observation that a signed-in customer changes a record identifier and sees another customer's invoice.
Incorrect Answers
A:Sensitive fields remain exposed when authorization and output filtering occur only in the browser; that evidence is relevant when a customer profile endpoint returns staff-only flags and internal identifiers even though the UI hides them, but does not establish closure of the object-level authorization flaw exposure.
C:Function authorization requires server-side role checks independent of hidden menus or client display logic; that evidence is relevant when a regular user reaches an administrator-only action by directly calling its API route, but does not establish closure of the object-level authorization flaw exposure.
D:Open redirect registration can misdeliver authorization responses or codes outside the intended client origin; that evidence is relevant when an authentication broker accepts an attacker-specified redirect destination when issuing authorization responses, but does not establish closure of the object-level authorization flaw exposure.
Question 605
The assessment lead requests a precise definition of configuration benchmark drift. Which technical interpretation fits?
- Authenticated assessments can inspect installed software and local configuration beyond remote service fingerprints.
- Unauthenticated checks evaluate externally observable attack surfaces but may lack host-level configuration detail.
- A false positive reports a weakness that is not actually present on the assessed asset.
- Configuration drift exposes services even when software is fully patched and scanner signatures are clean.
Explanation
Correct Answer
D:A server's approved security baseline disables a legacy protocol, but a local setting re-enables it; that situation illustrates the actual operating behavior under review. Its practical safeguard is to continuously compare runtime settings with approved security configuration baselines, with confirmation when a subsequent compliance check verifies the legacy protocol is disabled on every affected host.
Incorrect Answers
A:A network-only scanner misses an outdated package visible in the server's local package inventory; those details characterize credentialed vulnerability assessment and would call for use narrowly scoped protected scan credentials to collect host configuration and patch evidence, rather than explaining configuration benchmark drift.
B:A defender wants to know which flaws are visible to an outsider who has no internal credentials; those details characterize unauthenticated exposure assessment and would call for run approved external-facing assessments and record their limited visibility in risk results, rather than explaining configuration benchmark drift.
C:A scan flags vulnerable software, but a signed vendor inventory shows the affected component is not installed; those details characterize scanner false positive and would call for validate scanner claims against authoritative configurations and document disposition with evidence, rather than explaining configuration benchmark drift.
Question 606
The scope-approved analysis reports: An analysis device sees a copy of wire traffic without being assigned a production forwarding role. Which issue or method is primarily illustrated?
- Passive network tap
- ARP poisoning indicators
- TLS packet confidentiality
- DNS spoofing detection
- Rogue DHCP response
Explanation
Correct Answer
A:A passive tap observes link traffic independently of a switch's destination-based mirror configuration; that mechanism makes this classification more precise than the neighboring terms. The protective follow-up is to install taps only on approved links with capacity and access safeguards for captured data, verified when tap health and capture records confirm the monitored link's traffic is represented as intended.
Incorrect Answers
B:Forged ARP mappings can redirect local IPv4 frames through an unintended intermediary; this different classification would fit when several hosts suddenly associate the default gateway IPv4 address with an unfamiliar MAC address, not the evidence pointing to passive network tap in the question.
C:Properly negotiated TLS encrypts application data in transit, while some endpoint and connection metadata remain visible; this different classification would fit when a traffic capture contains TLS-encrypted application records but no readable credentials or request body, not the evidence pointing to passive network tap in the question.
D:Spoofed or poisoned DNS responses can misdirect clients without changing the intended application name; this different classification would fit when a resolver returns an unexpected destination address for a sensitive internal domain after a local network change, not the evidence pointing to passive network tap in the question.
E:Untrusted DHCP offers can redirect client network configuration toward attacker-controlled infrastructure; this different classification would fit when a desktop receives an address lease offering an unfamiliar gateway from an unauthorized switch port, not the evidence pointing to passive network tap in the question.
Question 607
A client requests practical treatment for this condition: A browser extension can read an authentication cookie because the cookie lacks appropriate client-side protections. Which measure is the closest match?
- Invalidate server-side session state and revoke relevant refresh tokens on logout.
- Choose an appropriate SameSite policy and independently protect state-changing requests against CSRF.
- Protect session cookies with HttpOnly and Secure attributes and enforce TLS transport.
- Use anti-CSRF tokens and suitable SameSite cookie restrictions on state-changing operations.
Explanation
Correct Answer
C:An accessible session token can be replayed to impersonate an authenticated browser session if stolen; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that browser inspection shows the session cookie is not script-readable and is sent only over HTTPS.
Incorrect Answers
A:Client-side cookie deletion alone may not revoke server-recognized sessions or long-lived tokens; the proposed safeguard addresses a case where a user clicks logout, but a copied access token continues authorizing API requests until its original expiry, rather than the exposed session cookie finding described here.
B:SameSite controls when browsers attach cookies to cross-site requests, reducing some ambient-authentication abuse; the proposed safeguard addresses a case where a cross-site navigation unexpectedly includes a privileged session cookie in a request to an internal application, rather than the exposed session cookie finding described here.
D:CSRF abuses ambient browser credentials when the application fails to verify the user's request intent; the proposed safeguard addresses a case where a logged-in user's browser submits a state-changing request after visiting an unrelated malicious page, rather than the exposed session cookie finding described here.
Question 608
An analyst is sorting findings by mechanism. One entry reads: An application URL-fetching feature can connect to instance-local metadata addresses from inside a cloud workload. Which label is the right one?
- Cloud metadata service exposure
- Cloud shared responsibility
- Cloud secrets distribution
- Cloud security posture assessment
Explanation
Correct Answer
A:Instance metadata endpoints may expose workload credentials when SSRF reaches them without effective isolation; that mechanism makes this classification more precise than the neighboring terms. The protective follow-up is to constrain server-side requests and enable hardened metadata access features where available, verified when controlled URL fetches cannot reach instance metadata and temporary credentials remain inaccessible.
Incorrect Answers
B:Cloud service providers secure assigned infrastructure layers while customers remain accountable for their configurations and data; this different classification would fit when a hosted database customer assumes the provider also determines application user permissions and data retention, not the evidence pointing to cloud metadata service exposure in the question.
C:Centralized secrets services support scoped retrieval and lifecycle controls instead of source-controlled credentials; this different classification would fit when multiple microservices copy shared database credentials into environment files committed with deployment manifests, not the evidence pointing to cloud metadata service exposure in the question.
D:Cloud security posture management compares cloud settings with policy baselines and aggregates misconfiguration findings; this different classification would fit when an organization wants continuous visibility into risky storage, identity, and network configurations across many accounts, not the evidence pointing to cloud metadata service exposure in the question.
Question 609
The team is closing an assessment finding: Multiple microservices copy shared database credentials into environment files committed with deployment manifests. What measure is most appropriate to implement?
- Use a managed key service with limited decrypt grants and remove exposed embedded keys.
- Limit administrative ingress to approved bastion or management source ranges.
- Use secret management with workload identity and limit retrieval to the requesting application.
- Constrain server-side requests and enable hardened metadata access features where available.
Explanation
Correct Answer
C:Centralized secrets services support scoped retrieval and lifecycle controls instead of source-controlled credentials; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that pipeline scans contain no live passwords and secret access logs map retrieval to approved workloads.
Incorrect Answers
A:Managed key services help separate protected key access, rotation policy, and audit from application source code; the proposed safeguard addresses a case where application data is encrypted but the same long-lived encryption key is hardcoded into its source repository, rather than the cloud secrets distribution finding described here.
B:Cloud workload firewalls or security groups constrain permitted instance traffic and may track connection state; the proposed safeguard addresses a case where a virtual machine accepts administrative traffic from every internet address because of an overly broad inbound rule, rather than the cloud secrets distribution finding described here.
D:Instance metadata endpoints may expose workload credentials when SSRF reaches them without effective isolation; the proposed safeguard addresses a case where an application URL-fetching feature can connect to instance-local metadata addresses from inside a cloud workload, rather than the cloud secrets distribution finding described here.
Question 610
An analyst is sorting findings by mechanism. One entry reads: A query value is copied into an HTML response and interpreted by the browser as executable markup. Which label is the right one?
- Cross-site request forgery in forms
- Stored cross-site scripting
- Excessive API response data
- Reflected cross-site scripting
Explanation
Correct Answer
D:Reflected XSS occurs when request-derived content is immediately returned without suitable output encoding; that mechanism makes this classification more precise than the neighboring terms. The protective follow-up is to apply context-appropriate output encoding and avoid inserting untrusted input into executable HTML contexts, verified when controlled request strings appear escaped in the reflected response and do not run as browser code.
Incorrect Answers
A:State-changing form endpoints are vulnerable when ambient cookies alone authorize cross-origin requests; this different classification would fit when a browser submits a password-change form while the user is logged in but without evidence of intended action, not the evidence pointing to reflected cross-site scripting in the question.
B:Stored XSS persists attacker-controlled content server-side and executes when it is later rendered unsafely; this different classification would fit when untrusted comment content executes in other users' browsers when a discussion page renders saved posts, not the evidence pointing to reflected cross-site scripting in the question.
C:Sensitive fields remain exposed when authorization and output filtering occur only in the browser; this different classification would fit when a customer profile endpoint returns staff-only flags and internal identifiers even though the UI hides them, not the evidence pointing to reflected cross-site scripting in the question.