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

Question 770

To limit storage duration for sensitive network traces after an investigation, which practice addresses that objective?

  1. Packet capture retention policy
  2. NetFlow top talkers
  3. SNMP interface trend
  4. Traffic mirror audit
  5. Network anomaly alert correlation

Explanation

Correct Answer

A:

Documented retention ensures useful evidence remains while unnecessary content is deleted on schedule; that is why it addresses the operational task to limit storage duration for sensitive network traces after an investigation.

Incorrect Answers

B:

Ranked flow summaries highlight traffic contributors for authorization and capacity review; a team would select it to identify hosts producing disproportionate outbound bytes on a WAN circuit, which does not provide the particular result to limit storage duration for sensitive network traces after an investigation.

C:

Counter polling provides long-term link statistics if rollover and sampling are handled correctly; its operational purpose is to compare switch utilization across several weeks of routine operation, not to achieve the specific requirement to limit storage duration for sensitive network traces after an investigation.

D:

Mirror source and destination settings determine visibility, independent of the sensor's detection rules; applying it would serve verify the monitoring configuration includes both directions of a critical VLAN without directly satisfying the goal to limit storage duration for sensitive network traces after an investigation.

E:

Combining flow, DNS, identity and change evidence improves signal precision; it addresses the different need to decide whether a new destination is malicious or part of an approved rollout, leaving the requested ability to limit storage duration for sensitive network traces after an investigation unresolved.

Question 771

To retain router and firewall security events away from potentially compromised devices, which tool, policy, or technique is appropriate?

  1. Encrypted log transport
  2. Append-only logging storage
  3. Centralized syslog forwarding
  4. Time synchronization monitoring

Explanation

Correct Answer

C:

Off-device collection supports cross-system correlation and protects evidence when local logs are lost; its relevant protective or investigative effect is to retain router and firewall security events away from potentially compromised devices.

Incorrect Answers

A:

TLS or equivalent authenticated channels mitigate transit disclosure and modification of security records; it could help someone trying to protect sensitive log entries crossing an untrusted operations network, but the problem is instead to retain router and firewall security events away from potentially compromised devices.

B:

Restricted write paths preserve previous records while retention and privileged controls remain important; that is useful when the task is to make it harder for ordinary administrators to rewrite past security events, not the stated requirement to retain router and firewall security events away from potentially compromised devices.

D:

Trusted NTP sources minimize clock drift that would otherwise confuse correlation; its operational purpose is to ensure independent device alerts can be ordered into one incident timeline, not to achieve the specific requirement to retain router and firewall security events away from potentially compromised devices.

Question 772

To protect sensitive log entries crossing an untrusted operations network, what safeguard would be most applicable?

  1. Log retention policy
  2. Centralized syslog forwarding
  3. Append-only logging storage
  4. Encrypted log transport

Explanation

Correct Answer

D:

TLS or equivalent authenticated channels mitigate transit disclosure and modification of security records; the requested outcome is precisely to protect sensitive log entries crossing an untrusted operations network.

Incorrect Answers

A:

Retention windows reflect business, legal and forensic requirements with protected disposition; although relevant to keep sufficient records for investigations without indefinite personal-data storage, it does not by itself achieve the required task to protect sensitive log entries crossing an untrusted operations network.

B:

Off-device collection supports cross-system correlation and protects evidence when local logs are lost; it could help someone trying to retain router and firewall security events away from potentially compromised devices, but the problem is instead to protect sensitive log entries crossing an untrusted operations network.

C:

Restricted write paths preserve previous records while retention and privileged controls remain important; that is useful when the task is to make it harder for ordinary administrators to rewrite past security events, not the stated requirement to protect sensitive log entries crossing an untrusted operations network.

Question 773

To ensure independent device alerts can be ordered into one incident timeline, what is the relevant defensive action?

  1. Time synchronization monitoring
  2. Encrypted log transport
  3. Centralized syslog forwarding
  4. Log retention policy

Explanation

Correct Answer

A:

Trusted NTP sources minimize clock drift that would otherwise confuse correlation; this choice fits the scenario because the team must ensure independent device alerts can be ordered into one incident timeline.

Incorrect Answers

B:

TLS or equivalent authenticated channels mitigate transit disclosure and modification of security records; although relevant to protect sensitive log entries crossing an untrusted operations network, it does not by itself achieve the required task to ensure independent device alerts can be ordered into one incident timeline.

C:

Off-device collection supports cross-system correlation and protects evidence when local logs are lost; it could help someone trying to retain router and firewall security events away from potentially compromised devices, but the problem is instead to ensure independent device alerts can be ordered into one incident timeline.

D:

Retention windows reflect business, legal and forensic requirements with protected disposition; that is useful when the task is to keep sufficient records for investigations without indefinite personal-data storage, not the stated requirement to ensure independent device alerts can be ordered into one incident timeline.

Question 774

To make it harder for ordinary administrators to rewrite past security events, which option most directly provides the capability?

  1. Log integrity signatures
  2. Encrypted log transport
  3. Log parsing normalization
  4. Append-only logging storage

Explanation

Correct Answer

D:

Restricted write paths preserve previous records while retention and privileged controls remain important; this mechanism directly supports the requirement to make it harder for ordinary administrators to rewrite past security events.

Incorrect Answers

A:

Cryptographic verification establishes tamper evidence when keys and original digest records are protected; its mechanism supports detect altered exported audit records through independently verifiable signatures, while the requested control must be able to make it harder for ordinary administrators to rewrite past security events.

B:

TLS or equivalent authenticated channels mitigate transit disclosure and modification of security records; the outcome it supports is to protect sensitive log entries crossing an untrusted operations network, whereas this scenario asks defenders to make it harder for ordinary administrators to rewrite past security events.

C:

Normalization aligns source, action, timestamp and identity attributes for consistent searching; although relevant to map different firewall vendor fields into a common event schema, it does not by itself achieve the required task to make it harder for ordinary administrators to rewrite past security events.

Question 775

To keep sufficient records for investigations without indefinite personal-data storage, which control achieves the target outcome?

  1. Alert severity calibration
  2. Log retention policy
  3. Encrypted log transport
  4. Log parsing normalization
  5. Security event correlation

Explanation

Correct Answer

B:

Retention windows reflect business, legal and forensic requirements with protected disposition; it supplies the specific control needed to keep sufficient records for investigations without indefinite personal-data storage.

Incorrect Answers

A:

Tuned severity considers asset importance, confidence and observable impact instead of raw event counts; the technique works for situations involving reduce priority inflation from frequent low-impact authentication failures, rather than this need to keep sufficient records for investigations without indefinite personal-data storage.

C:

TLS or equivalent authenticated channels mitigate transit disclosure and modification of security records; the outcome it supports is to protect sensitive log entries crossing an untrusted operations network, whereas this scenario asks defenders to keep sufficient records for investigations without indefinite personal-data storage.

D:

Normalization aligns source, action, timestamp and identity attributes for consistent searching; although relevant to map different firewall vendor fields into a common event schema, it does not by itself achieve the required task to keep sufficient records for investigations without indefinite personal-data storage.

E:

Correlating multiple log sources supplies context unavailable in isolated single-product alerts; it could help someone trying to link one identity's failed VPN logins to subsequent server access, but the problem is instead to keep sufficient records for investigations without indefinite personal-data storage.

Question 776

To map different firewall vendor fields into a common event schema, which solution should be adopted?

  1. Sensitive log redaction
  2. Log integrity signatures
  3. Log parsing normalization
  4. Log retention policy

Explanation

Correct Answer

C:

Normalization aligns source, action, timestamp and identity attributes for consistent searching; that is why it addresses the operational task to map different firewall vendor fields into a common event schema.

Incorrect Answers

A:

Field-level sanitization preserves useful events without accumulating additional high-value secrets; it addresses the different need to avoid storing session tokens or full personal records in diagnostic messages, leaving the requested ability to map different firewall vendor fields into a common event schema unresolved.

B:

Cryptographic verification establishes tamper evidence when keys and original digest records are protected; the technique works for situations involving detect altered exported audit records through independently verifiable signatures, rather than this need to map different firewall vendor fields into a common event schema.

D:

Retention windows reflect business, legal and forensic requirements with protected disposition; the outcome it supports is to keep sufficient records for investigations without indefinite personal-data storage, whereas this scenario asks defenders to map different firewall vendor fields into a common event schema.

Question 777

To link one identity's failed VPN logins to subsequent server access, which of the available controls is suitable?

  1. Alert severity calibration
  2. Security event correlation
  3. Log retention policy
  4. Log integrity signatures

Explanation

Correct Answer

B:

Correlating multiple log sources supplies context unavailable in isolated single-product alerts; its relevant protective or investigative effect is to link one identity's failed VPN logins to subsequent server access.

Incorrect Answers

A:

Tuned severity considers asset importance, confidence and observable impact instead of raw event counts; applying it would serve reduce priority inflation from frequent low-impact authentication failures without directly satisfying the goal to link one identity's failed VPN logins to subsequent server access.

C:

Retention windows reflect business, legal and forensic requirements with protected disposition; the technique works for situations involving keep sufficient records for investigations without indefinite personal-data storage, rather than this need to link one identity's failed VPN logins to subsequent server access.

D:

Cryptographic verification establishes tamper evidence when keys and original digest records are protected; its mechanism supports detect altered exported audit records through independently verifiable signatures, while the requested control must be able to link one identity's failed VPN logins to subsequent server access.

Question 778

To reduce priority inflation from frequent low-impact authentication failures and to detect altered exported audit records through independently verifiable signatures, which TWO measures should the defender select? Choose TWO.

  1. Alert severity calibration
  2. Log integrity signatures
  3. Log retention policy
  4. Sensitive log redaction
  5. Logging pipeline health alert

Explanation

Correct Answers

A:

Tuned severity considers asset importance, confidence and observable impact instead of raw event counts; its contribution to the combined design is specifically to reduce priority inflation from frequent low-impact authentication failures.

B:

Cryptographic verification establishes tamper evidence when keys and original digest records are protected; its contribution to the combined design is specifically to detect altered exported audit records through independently verifiable signatures.

Incorrect Answers

C:

Retention windows reflect business, legal and forensic requirements with protected disposition; it addresses the different need to keep sufficient records for investigations without indefinite personal-data storage, leaving the requested ability to reduce priority inflation from frequent low-impact authentication failures and to detect altered exported audit records through independently verifiable signatures unresolved.

D:

Field-level sanitization preserves useful events without accumulating additional high-value secrets; the technique works for situations involving avoid storing session tokens or full personal records in diagnostic messages, rather than this need to reduce priority inflation from frequent low-impact authentication failures and to detect altered exported audit records through independently verifiable signatures.

E:

Ingestion-heartbeat monitoring distinguishes quiet systems from failed collection paths; its mechanism supports detect a branch firewall that suddenly stops sending any events, while the requested control must be able to reduce priority inflation from frequent low-impact authentication failures and to detect altered exported audit records through independently verifiable signatures.

Question 779

To detect altered exported audit records through independently verifiable signatures, which approach should a security logging engineer choose?

  1. Sensitive log redaction
  2. Log parsing normalization
  3. Logging pipeline health alert
  4. Security event correlation
  5. Log integrity signatures
  6. Append-only logging storage

Explanation

Correct Answer

E:

Cryptographic verification establishes tamper evidence when keys and original digest records are protected; this choice fits the scenario because the team must detect altered exported audit records through independently verifiable signatures.

Incorrect Answers

A:

Field-level sanitization preserves useful events without accumulating additional high-value secrets; a team would select it to avoid storing session tokens or full personal records in diagnostic messages, which does not provide the particular result to detect altered exported audit records through independently verifiable signatures.

B:

Normalization aligns source, action, timestamp and identity attributes for consistent searching; its operational purpose is to map different firewall vendor fields into a common event schema, not to achieve the specific requirement to detect altered exported audit records through independently verifiable signatures.

C:

Ingestion-heartbeat monitoring distinguishes quiet systems from failed collection paths; applying it would serve detect a branch firewall that suddenly stops sending any events without directly satisfying the goal to detect altered exported audit records through independently verifiable signatures.

D:

Correlating multiple log sources supplies context unavailable in isolated single-product alerts; it addresses the different need to link one identity's failed VPN logins to subsequent server access, leaving the requested ability to detect altered exported audit records through independently verifiable signatures unresolved.

F:

Restricted write paths preserve previous records while retention and privileged controls remain important; its mechanism supports make it harder for ordinary administrators to rewrite past security events, while the requested control must be able to detect altered exported audit records through independently verifiable signatures.

Question 780

To detect a branch firewall that suddenly stops sending any events, which method is designed for the task?

  1. Logging pipeline health alert
  2. Sensitive log redaction
  3. Log parsing normalization
  4. Alert severity calibration
  5. Security event correlation

Explanation

Correct Answer

A:

Ingestion-heartbeat monitoring distinguishes quiet systems from failed collection paths; this mechanism directly supports the requirement to detect a branch firewall that suddenly stops sending any events.

Incorrect Answers

B:

Field-level sanitization preserves useful events without accumulating additional high-value secrets; a team would select it to avoid storing session tokens or full personal records in diagnostic messages, which does not provide the particular result to detect a branch firewall that suddenly stops sending any events.

C:

Normalization aligns source, action, timestamp and identity attributes for consistent searching; its operational purpose is to map different firewall vendor fields into a common event schema, not to achieve the specific requirement to detect a branch firewall that suddenly stops sending any events.

D:

Tuned severity considers asset importance, confidence and observable impact instead of raw event counts; applying it would serve reduce priority inflation from frequent low-impact authentication failures without directly satisfying the goal to detect a branch firewall that suddenly stops sending any events.

E:

Correlating multiple log sources supplies context unavailable in isolated single-product alerts; it addresses the different need to link one identity's failed VPN logins to subsequent server access, leaving the requested ability to detect a branch firewall that suddenly stops sending any events unresolved.

Certified Network Defender (312-38) Practice Tests