ECCouncil 312-38 (Certified Network Defender) Practice Test 31

Question 300

A web portal needs a browser-enforced restriction on which script origins may execute after an HTML injection attempt. Which web application defense should the team implement?

  1. Anti-CSRF request token
  2. Content Security Policy
  3. Parameterized database queries
  4. Strict server-side input validation
  5. Contextual output encoding

Explanation

Correct Answer

B:

CSP restricts permitted content sources and can reduce some script injection impacts, especially with nonces and strict policies. It complements output encoding.

Incorrect Answers

A:

Server-validated anti-CSRF tokens tie state-changing requests to authorized interaction and session context for the specific concern of distinguishing intended state-changing browser requests, not the requirement involving permitted script origins in browser.

C:

Prepared statements separate SQL commands from variable input values, preventing data from becoming executable query syntax; the operational difference is separating untrusted input from SQL structure versus the scenario's permitted script origins in browser.

D:

Server-side validation enforces business rules regardless of client behavior; its distinguishing scope is validation outside attacker-controlled browser, not the reported permitted script origins in browser.

E:

Encoding untrusted values for the exact output context prevents them from being interpreted as active browser code; this characterizes preventing user content from executing in browser, whereas the reported condition is permitted script origins in browser.

Question 301

An API endpoint has a precise schema and should reject requests outside its defined methods, content types and field structures. Which web application firewall strategy fits the operational condition?

  1. Positive security model
  2. Virtual patching rule
  3. Rate limiting at API gateway
  4. WAF monitor-only policy

Explanation

Correct Answer

A:

A positive model accepts traffic matching approved behavior rather than matching only known malicious patterns. Tuning requires accurate application knowledge.

Incorrect Answers

B:

A narrowly tuned WAF rule can reduce exploitation exposure until software remediation is applied for the specific concern of interim filtering for an unfixed flaw, not the requirement involving allow only schema-conformant HTTP input.

C:

Rate limiting constrains request frequency by keys or identities when the underlying evidence concerns request frequency controls on API endpoint rather than the stated allow only schema-conformant HTTP input.

D:

Detection-only mode logs would-be matches so operators can calibrate rules using actual legitimate traffic in a setting defined by assess false positives before WAF enforcement; the observed issue is allow only schema-conformant HTTP input.

Question 302

Operators want detection rules that reject recognizable malicious request patterns while allowing most otherwise unknown application requests. Which web application firewall strategy fits the operational condition?

  1. Negative signature model
  2. Rate limiting at API gateway
  3. WAF monitor-only policy
  4. Positive security model

Explanation

Correct Answer

A:

Negative security rules match known hostile features such as injection signatures. They can miss novel encodings and cause false positives.

Incorrect Answers

B:

Rate limiting constrains request frequency by keys or identities when the underlying evidence concerns request frequency controls on API endpoint rather than the stated blocking recognized hostile web patterns.

C:

Detection-only mode logs would-be matches so operators can calibrate rules using actual legitimate traffic in a setting defined by assess false positives before WAF enforcement; the observed issue is blocking recognized hostile web patterns.

D:

A positive model accepts traffic matching approved behavior rather than matching only known malicious patterns; its distinguishing scope is allow only schema-conformant HTTP input, not the reported blocking recognized hostile web patterns.

Question 303

A public application cannot be patched immediately and the team needs temporary filtering of requests that exploit a known vulnerable endpoint. Which web application firewall strategy fits the operational condition?

  1. Negative signature model
  2. WAF monitor-only policy
  3. Virtual patching rule
  4. Positive security model

Explanation

Correct Answer

C:

A narrowly tuned WAF rule can reduce exploitation exposure until software remediation is applied. It does not remove the vulnerable code.

Incorrect Answers

A:

Negative security rules match known hostile features such as injection signatures in a setting defined by blocking recognized hostile web patterns; the observed issue is interim filtering for an unfixed flaw.

B:

Detection-only mode logs would-be matches so operators can calibrate rules using actual legitimate traffic in a setting defined by assess false positives before WAF enforcement; the observed issue is interim filtering for an unfixed flaw.

D:

A positive model accepts traffic matching approved behavior rather than matching only known malicious patterns for situations characterized by allow only schema-conformant HTTP input; the case points instead to interim filtering for an unfixed flaw.

Question 304

A login endpoint receives excessive automated requests and should enforce per-client request quotas without disabling the service. Which web application firewall strategy fits the operational condition?

  1. Negative signature model
  2. WAF monitor-only policy
  3. Virtual patching rule
  4. Rate limiting at API gateway

Explanation

Correct Answer

D:

Rate limiting constrains request frequency by keys or identities. Distributed attackers may require layered controls and abuse analytics.

Incorrect Answers

A:

Negative security rules match known hostile features such as injection signatures; its distinguishing scope is blocking recognized hostile web patterns, not the reported request frequency controls on API endpoint.

B:

Detection-only mode logs would-be matches so operators can calibrate rules using actual legitimate traffic; its distinguishing scope is assess false positives before WAF enforcement, not the reported request frequency controls on API endpoint.

C:

A narrowly tuned WAF rule can reduce exploitation exposure until software remediation is applied in a setting defined by interim filtering for an unfixed flaw; the observed issue is request frequency controls on API endpoint.

Question 305

New HTTP inspection rules might reject legitimate checkout requests and need a production observation period before blocking. Which web application firewall strategy fits the operational condition?

  1. WAF monitor-only policy
  2. Virtual patching rule
  3. Rate limiting at API gateway
  4. Positive security model
  5. Negative signature model

Explanation

Correct Answer

A:

Detection-only mode logs would-be matches so operators can calibrate rules using actual legitimate traffic. It does not actively stop the matched requests.

Incorrect Answers

B:

A narrowly tuned WAF rule can reduce exploitation exposure until software remediation is applied in a setting defined by interim filtering for an unfixed flaw; the observed issue is assess false positives before WAF enforcement.

C:

Rate limiting constrains request frequency by keys or identities when analysts encounter request frequency controls on API endpoint; this question instead describes assess false positives before WAF enforcement.

D:

A positive model accepts traffic matching approved behavior rather than matching only known malicious patterns when the underlying evidence concerns allow only schema-conformant HTTP input rather than the stated assess false positives before WAF enforcement.

E:

Negative security rules match known hostile features such as injection signatures for the specific concern of blocking recognized hostile web patterns, not the requirement involving assess false positives before WAF enforcement.

Question 306

Developers want source-code analysis that highlights dangerous data flows before an application is deployed or running. Which software-delivery security measure best matches this need?

  1. Software supply-chain signing
  2. Static application security testing
  3. Security testing in CI pipeline
  4. Secret scanning in source control

Explanation

Correct Answer

B:

SAST examines code or intermediate representations for vulnerability patterns. Findings require triage to distinguish reachable flaws from noise.

Incorrect Answers

A:

Artifact signing binds an artifact digest to a trusted signer or provenance, supporting integrity checks at deployment when analysts encounter authentication of build artifacts before release; this question instead describes source-oriented flaw detection before runtime.

C:

CI integration runs suitable security tests during development and blocks or flags changes based on defined policy for situations characterized by repeatable pre-merge security checks; the case points instead to source-oriented flaw detection before runtime.

D:

Secret scanning detects credential-like values in commits and repositories; the operational difference is detection of committed authentication secrets versus the scenario's source-oriented flaw detection before runtime.

Question 307

Testers must discover web vulnerabilities by sending requests to a running staging application without analyzing its source. Which software-delivery security measure best matches this need?

  1. Software supply-chain signing
  2. Dynamic application security testing
  3. Static application security testing
  4. Security testing in CI pipeline

Explanation

Correct Answer

B:

DAST probes live application behavior through its interface and can reveal exploitable runtime conditions. Coverage depends on paths exercised.

Incorrect Answers

A:

Artifact signing binds an artifact digest to a trusted signer or provenance, supporting integrity checks at deployment; it handles authentication of build artifacts before release, while the decisive evidence in the question is runtime black-box web probing.

C:

SAST examines code or intermediate representations for vulnerability patterns; that is relevant to source-oriented flaw detection before runtime but does not directly account for runtime black-box web probing.

D:

CI integration runs suitable security tests during development and blocks or flags changes based on defined policy when the underlying evidence concerns repeatable pre-merge security checks rather than the stated runtime black-box web probing.

Question 308

A developer pushes an API password into a repository and the organization wants automated identification before it spreads. Which software-delivery security measure best matches this need?

  1. Secret scanning in source control
  2. Software supply-chain signing
  3. Security testing in CI pipeline
  4. Dynamic application security testing

Explanation

Correct Answer

A:

Secret scanning detects credential-like values in commits and repositories. Exposed credentials still need revocation and replacement.

Incorrect Answers

B:

Artifact signing binds an artifact digest to a trusted signer or provenance, supporting integrity checks at deployment; its distinguishing scope is authentication of build artifacts before release, not the reported detection of committed authentication secrets.

C:

CI integration runs suitable security tests during development and blocks or flags changes based on defined policy when the underlying evidence concerns repeatable pre-merge security checks rather than the stated detection of committed authentication secrets.

D:

DAST probes live application behavior through its interface and can reveal exploitable runtime conditions in a setting defined by runtime black-box web probing; the observed issue is detection of committed authentication secrets.

Question 309

Release managers must verify that deployment artifacts come from an approved build process and have not changed in transit. Which software-delivery security measure best matches this need?

  1. Software supply-chain signing
  2. Dynamic application security testing
  3. Static application security testing
  4. Secret scanning in source control

Explanation

Correct Answer

A:

Artifact signing binds an artifact digest to a trusted signer or provenance, supporting integrity checks at deployment.

Incorrect Answers

B:

DAST probes live application behavior through its interface and can reveal exploitable runtime conditions; it handles runtime black-box web probing, while the decisive evidence in the question is authentication of build artifacts before release.

C:

SAST examines code or intermediate representations for vulnerability patterns; it handles source-oriented flaw detection before runtime, while the decisive evidence in the question is authentication of build artifacts before release.

D:

Secret scanning detects credential-like values in commits and repositories when analysts encounter detection of committed authentication secrets; this question instead describes authentication of build artifacts before release.

Question 310

Security issues are repeatedly found only after releases, and the team wants automated checks on each proposed code change. Which software-delivery security measure best matches this need?

  1. Dynamic application security testing
  2. Software supply-chain signing
  3. Security testing in CI pipeline
  4. Secret scanning in source control
  5. Static application security testing

Explanation

Correct Answer

C:

CI integration runs suitable security tests during development and blocks or flags changes based on defined policy. Review is still needed for complex findings.

Incorrect Answers

A:

DAST probes live application behavior through its interface and can reveal exploitable runtime conditions; it handles runtime black-box web probing, while the decisive evidence in the question is repeatable pre-merge security checks.

B:

Artifact signing binds an artifact digest to a trusted signer or provenance, supporting integrity checks at deployment; this characterizes authentication of build artifacts before release, whereas the reported condition is repeatable pre-merge security checks.

D:

Secret scanning detects credential-like values in commits and repositories; it handles detection of committed authentication secrets, while the decisive evidence in the question is repeatable pre-merge security checks.

E:

SAST examines code or intermediate representations for vulnerability patterns for situations characterized by source-oriented flaw detection before runtime; the case points instead to repeatable pre-merge security checks.

Certified Network Defender (312-38) Practice Tests