Question 830
An analyst is explaining compensating control to a system owner. Which description is technically correct?
- Compensating safeguards lower exposure when the primary fix is temporarily infeasible without removing the defect.
- CVSS communicates technical severity characteristics and is not, by itself, a full organization-specific risk score.
- Security patch completion requires both removal of the defect and preservation of required functionality.
- Risk-based remediation SLAs translate vulnerability priority into accountable response deadlines and escalation.
Explanation
Correct Answer
A:An obsolete appliance cannot be patched immediately, but traffic to its management service can be limited; that situation illustrates the actual operating behavior under review. Its practical safeguard is to apply restrictive access controls and a time-bound, approved remediation exception, with confirmation when connection tests prove isolation is effective and a tracked replacement deadline remains assigned.
Incorrect Answers
B:A vulnerability report uses a standardized severity number without considering whether the vulnerable system is exposed; those details characterize CVSS impact scoring and would call for combine standardized severity with reachability, asset impact, and compensating controls, rather than explaining compensating control.
C:After a patch deployment, the vulnerable version disappears but the application fails its normal health check; those details characterize patch regression validation and would call for reassess vulnerability state and run targeted operational regression checks after deployment, rather than explaining compensating control.
D:A critical finding stays open for months because no team owns the fix or deadline; those details characterize remediation service level and would call for assign remediation owners and deadlines that reflect verified business exposure and severity, rather than explaining compensating control.
Question 831
The assessment lead requests a precise definition of parameterized SQL execution. Which technical interpretation fits?
- Parameter binding separates query structure from untrusted values, preventing data from becoming SQL syntax.
- Second-order injection arises when previously persisted untrusted content becomes executable query syntax downstream.
- SQL parameters generally bind values, not arbitrary identifiers such as table or column names.
- Blind SQL injection can reveal information through application behavior or timing even when direct query output is hidden.
Explanation
Correct Answer
A:An application builds database queries by concatenating search text into the SQL statement itself; that situation illustrates the actual operating behavior under review. Its practical safeguard is to use prepared statements with bound parameters for user-supplied values, with confirmation when tests with SQL-like characters are processed as data without changing the query structure.
Incorrect Answers
B:Data safely stored as text later enters a different program's dynamic SQL construction without parameter binding; those details characterize second-order SQL injection and would call for parameterize every SQL execution point, including background processing of stored values, rather than explaining parameterized SQL execution.
C:An application lets a user choose a sort column and attempts to pass the column name as a value parameter; those details characterize dynamic SQL identifier safety and would call for select requested identifiers from an explicit server-side allowlist before composing the statement, rather than explaining parameterized SQL execution.
D:A test environment shows response differences based on conditional database behavior without displaying SQL errors; those details characterize blind injection inference and would call for remove injection flaws using parameter binding and ensure consistent error handling, rather than explaining parameterized SQL execution.
Question 832
Which audit observation best verifies a corrective measure covering IoT factory credentials?
- Cross-segment tests show cameras cannot reach protected business hosts or administrative services.
- Inventory tests show factory logins rejected and approved maintenance identities individually tracked.
- Passive sensor output matches known controller addresses without generating scan packets on the control network.
- Tampered firmware packages fail signature validation while approved updates install normally.
- The test plan documents safety approval and proves production controllers were not disrupted.
Explanation
Correct Answer
B:Factory credentials create predictable management access if they remain active after device commissioning; the outcome tests this precise property in the production control. It relates to the original observation that multiple smart sensors share an unchanged default administrative password across an entire facility.
Incorrect Answers
A:Connected devices with limited management assurance should not inherit unrestricted enterprise network trust; that evidence is relevant when an internet-connected camera can initiate sessions to corporate finance workstations, but does not establish closure of the IoT factory credentials exposure.
C:Passive discovery derives device roles and communications from existing traffic without injecting new requests; that evidence is relevant when a safety-critical network cannot tolerate unknown active probes, but operators need controller inventory, but does not establish closure of the IoT factory credentials exposure.
D:Unsigned update paths permit modified firmware to be accepted as if it were trusted vendor software; that evidence is relevant when a gateway installs downloaded firmware without checking that it came from an approved signer, but does not establish closure of the IoT factory credentials exposure.
E:Operational technology places physical safety and process continuity ahead of routine disruptive test coverage; that evidence is relevant when an assessor proposes aggressive availability testing against a live industrial controller during production, but does not establish closure of the IoT factory credentials exposure.
Question 833
In a security workshop about OT safety priority, which technical statement is valid?
- Traditional Modbus lacks inherent cryptographic identity and confidentiality protections on its own.
- PLC control interfaces affect physical processes and must be shielded from unauthorized enterprise traffic.
- Operational technology places physical safety and process continuity ahead of routine disruptive test coverage.
- Passive discovery derives device roles and communications from existing traffic without injecting new requests.
Explanation
Correct Answer
C:An assessor proposes aggressive availability testing against a live industrial controller during production; that situation illustrates the actual operating behavior under review. Its practical safeguard is to use an approved maintenance window, passive observation, or digital twin for hazardous assessments, with confirmation when the test plan documents safety approval and proves production controllers were not disrupted.
Incorrect Answers
A:A legacy industrial device exchanges control commands through a protocol with no built-in user authentication; those details characterize modbus authentication boundary and would call for compensate with network isolation, industrial-aware monitoring, and trusted control endpoints, rather than explaining OT safety priority.
B: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 OT safety priority.
D:A safety-critical network cannot tolerate unknown active probes, but operators need controller inventory; those details characterize passive OT asset discovery and would call for use mirrored OT traffic and correlate observed devices with engineering-owned inventory, rather than explaining OT safety priority.
Question 834
A finding concerns RDAP registration lookup. Select the explanation that captures how this issue or control works.
- DKIM binds selected message headers and body content to a signing domain using a published public key.
- MX records designate inbound mail exchanges and their relative delivery priorities.
- RDAP provides structured registration data over HTTPS with access controls and standardized responses.
- DMARC evaluates alignment with SPF or DKIM and lets the domain owner publish reporting and handling policy.
- Autonomous system registration and routing information connect public prefixes with network operators.
Explanation
Correct Answer
C:An asset owner wants standardized registration records for a domain without relying on old free-form WHOIS formatting; that situation illustrates the actual operating behavior under review. Its practical safeguard is to use registry-supported RDAP endpoints and respect redaction of personal contact fields, with confirmation when the returned structured record matches the domain registration and shows registry-provided status fields.
Incorrect Answers
A: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 RDAP registration lookup.
B:A mail delivery investigation needs to identify which hosts accept messages for the organization's domain; those details characterize DNS mx records and would call for keep published mail-routing records accurate and retire obsolete mail exchangers, rather than explaining RDAP registration lookup.
D:A mail security report shows messages rejected when visible sender identity fails domain alignment checks; those details characterize DMARC email alignment and would call for configure DMARC reporting and an enforcement policy appropriate to the domain's readiness, rather than explaining RDAP registration lookup.
E:A network researcher needs to distinguish an organization's routed address prefixes from a vendor's hosting range; those details characterize ASN ownership mapping and would call for reconcile public routing ownership with the authorized assessment scope before probing addresses, rather than explaining RDAP registration lookup.
Question 835
Which mechanism should a defender associate with enterprise mobile work profile?
- Mobile platform permissions restrict sensitive APIs, but users and administrators still must assess necessity.
- Managed work containers separate enterprise data and policies from personal applications where supported.
- Rooted or jailbroken devices may bypass normal sandbox boundaries and weaken enterprise assurance.
- Unreviewed side-loading increases exposure to modified packages and misleading publisher identities.
Explanation
Correct Answer
B:An employer wants to remove corporate email from a personally owned phone without erasing family photos; that situation illustrates the actual operating behavior under review. Its practical safeguard is to use a managed work profile or equivalent app-container policy for corporate information, with confirmation when retirement testing removes managed work data while leaving the user's personal files intact.
Incorrect Answers
A:A flashlight app asks for microphone, contact, and precise-location access without a relevant feature; those details characterize mobile permission minimization and would call for deny unrelated permissions and distribute apps through a reviewed enterprise catalog, rather than explaining enterprise mobile work profile.
C:A managed phone has modified its platform trust controls and can access protected application storage; those details characterize jailbreak and root exposure and would call for use posture checks and limit sensitive access from noncompliant devices without relying solely on root detection, rather than explaining enterprise mobile work profile.
D:Employees install a business lookalike app from an unknown APK source outside the approved enterprise catalog; those details characterize unmanaged app sideloading and would call for apply mobile application management and restrict unapproved package installation on managed devices, rather than explaining enterprise mobile work profile.
Question 836
A follow-up audit focuses on qr-code phishing. Which evidence most reliably demonstrates effective treatment?
- Transaction logs show the payment was held until callback validation and independent approval completed.
- Test scans confirm users recognize and reject unexpected external login domains.
- Endpoint device-control logs deny unknown USB storage without affecting approved peripherals.
- Test events show unsolicited approval requests are rejected and reported through the security channel.
- A controlled awareness test shows staff verify personalized urgent requests before submitting credentials.
Explanation
Correct Answer
B:QR-based phishing hides the destination inside an encoded image, making URL inspection less obvious; the outcome tests this precise property in the production control. It relates to the original observation that a poster's QR image opens a credential collection page while appearing to link to a visitor check-in.
Incorrect Answers
A:AI-generated voice imitation can mimic a trusted person's speech without proving caller identity or authority; that evidence is relevant when a caller sounds like the finance director and orders an urgent transfer, but the account details fail normal verification, but does not establish closure of the qr-code phishing exposure.
C:Physical baiting entices people to connect untrusted media or access tempting content; that evidence is relevant when an employee finds a labeled USB device in a public lobby that claims to contain staff bonuses, but does not establish closure of the qr-code 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 qr-code phishing exposure.
E:Spear phishing uses tailored context to make fraudulent communications appear personally relevant; that evidence is relevant when a forged message uses the recipient's project name and manager's identity to request a credential reset, but does not establish closure of the qr-code phishing exposure.
Question 837
A review board requests objective closure evidence for unsafe object deserialization. Which outcome should be supplied?
- Controlled request strings appear escaped in the reflected response and do not run as browser code.
- Malformed serialized input is rejected before dangerous object constructors or methods are invoked.
- Cross-account tests cannot access invoices belonging to a different customer even with known identifiers.
- Boundary tests cannot retrieve files above or outside the configured download directory.
- Requests to prohibited internal destinations are rejected before any backend network connection.
Explanation
Correct Answer
B:Deserialization of untrusted object graphs can trigger unsafe code paths or unexpected property changes; the outcome tests this precise property in the production control. It relates to the original observation that an application reconstructs complex server objects directly from untrusted client-supplied serialized data.
Incorrect Answers
A:Reflected XSS occurs when request-derived content is immediately returned without suitable output encoding; that evidence is relevant when a query value is copied into an HTML response and interpreted by the browser as executable markup, but does not establish closure of the unsafe object deserialization exposure.
C:Object-level authorization fails when the server trusts a client-chosen identifier without checking ownership; that evidence is relevant when a signed-in customer changes a record identifier and sees another customer's invoice, but does not establish closure of the unsafe object deserialization exposure.
D:Traversal occurs when user-controlled paths escape the allowed base directory after unsafe normalization; that evidence is relevant when a download endpoint accepts a filename with parent-directory components and reads outside its intended folder, but does not establish closure of the unsafe object deserialization exposure.
E:SSRF abuses a server's network privileges to request destinations inaccessible to the external client; that evidence is relevant when a document-preview service fetches an arbitrary URL supplied by a user and reaches internal-only resources, but does not establish closure of the unsafe object deserialization exposure.
Question 838
For the documented case, consider: A profile update API accepts an undocumented isAdmin property and writes it to the user record. Which specific defensive response is indicated?
- Treat retrieved content as untrusted data and enforce tool permissions and output validation outside the model.
- Enforce per-object access policy for every data retrieval and modification request.
- Check authorization on each privileged operation and deny unentitled roles server-side.
- Allowlist writable fields for each endpoint and enforce ownership and role restrictions.
Explanation
Correct Answer
D:Mass assignment arises when untrusted request fields bind directly to sensitive model properties; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that tests attempting to change privileged or internal properties are ignored or rejected.
Incorrect Answers
A:Indirect prompt injection places adversarial instructions in lower-trust content that a language model may incorrectly treat as authority; the proposed safeguard addresses a case where a web assistant begins following instructions embedded in a retrieved document instead of the user's authorized request, rather than the mass assignment flaw finding described here.
B:Object-level authorization fails when the server trusts a client-chosen identifier without checking ownership; the proposed safeguard addresses a case where a signed-in customer changes a record identifier and sees another customer's invoice, rather than the mass assignment flaw finding described here.
C:Function authorization requires server-side role checks independent of hidden menus or client display logic; the proposed safeguard addresses a case where a regular user reaches an administrator-only action by directly calling its API route, rather than the mass assignment flaw finding described here.
Question 839
Under an authorized engagement, the report states: An endpoint lists remotely exposed interface identifiers and service bindings to unknown clients. Which protective practice belongs in the fix plan?
- Require authorization on collection endpoints and restrict fields returned to each role.
- Separate public DNS data from private records and review externally published names.
- Use SNMPv3 authenticated encryption and limit permitted management stations.
- Restrict RPC management interfaces to trusted subnets and authorized authenticated clients.
- Disable unnecessary legacy name resolution and filter it across security boundaries.
Explanation
Correct Answer
D:RPC endpoint information can reveal reachable management interfaces and service dependencies; this is the specific exposure or dependency that the selected action addresses. After treatment, the assessor should confirm that network policy checks show public clients cannot query sensitive remote management bindings.
Incorrect Answers
A:Excessive API enumeration arises when list endpoints lack authorization or safe pagination and filtering; the proposed safeguard addresses a case where an administrative API lists internal user identifiers through an endpoint open to all clients, rather than the RPC service mapping finding described here.
B:DNS records may expose system naming and topology when public and internal views are mixed; the proposed safeguard addresses a case where an external reviewer learns internal-looking DNS names from a public-facing name service, rather than the RPC service mapping finding described here.
C:Legacy SNMP community strings act as weak shared access tokens, especially without encryption; the proposed safeguard addresses a case where a network device exposes interface and configuration information through a shared default community string, rather than the RPC service mapping finding described here.
E:Legacy NetBIOS name services can leak host inventory and administrative naming conventions; the proposed safeguard addresses a case where a legacy Windows segment reveals workstation names and workgroup identifiers through name-service responses, rather than the RPC service mapping finding described here.
Question 840
A remediation ticket for CoAP transport protection needs technical proof before closure. Which test result fits?
- Protocol captures verify readings are protected and unauthenticated peers cannot join the exchange.
- Tampered firmware packages fail signature validation while approved updates install normally.
- Update reports map each device to approved version, owner, rollout status, and exception.
- Passive sensor output matches known controller addresses without generating scan packets on the control network.
Explanation
Correct Answer
A:CoAP traffic needs an appropriate protected transport or object security design when data confidentiality matters; the outcome tests this precise property in the production control. It relates to the original observation that a constrained sensor sends sensitive readings over unprotected datagrams to an external aggregator.
Incorrect Answers
B:Unsigned update paths permit modified firmware to be accepted as if it were trusted vendor software; that evidence is relevant when a gateway installs downloaded firmware without checking that it came from an approved signer, but does not establish closure of the CoAP transport protection exposure.
C:Unmanaged update processes leave persistent known weaknesses in long-lived embedded deployments; that evidence is relevant when deployed devices receive security fixes inconsistently because no operator owns their update policy, but does not establish closure of the CoAP transport protection exposure.
D:Passive discovery derives device roles and communications from existing traffic without injecting new requests; that evidence is relevant when a safety-critical network cannot tolerate unknown active probes, but operators need controller inventory, but does not establish closure of the CoAP transport protection exposure.