ECCouncil 212-89 (EC-Council Certified Incident Handler) Practice Test 51

Question 500

Several endpoints make regular outbound HTTPS requests to a domain with no legitimate business purpose. Which assessment avoids the most important mistaken assumption here?

  1. Recognize staged payload retrieval rather than one static malware file
  2. Recognize beacon-like periodic communications as possible command-and-control
  3. Recognize DNS tunneling or encoded data movement as the key suspicion
  4. Recognize lateral reconnaissance rather than routine endpoint updating
  5. Recognize potential malware-assisted collection and exfiltration

Explanation

Correct Answer

B:

For assessment and interpretation involving “Recognize beacon-like periodic communications as” and the report “a domain with no legitimate business purpose”, repeated timed requests may represent remote tasking rather than interactive browsing. “Preserve proxy logs, DNS responses, endpoint processes and TLS metadata” is a check against premature conclusions.

Incorrect Answers

A:

For assessment and interpretation, contrasting “Recognize staged payload retrieval rather” with “a domain with no legitimate business purpose”, changing remote objects can deliver new execution stages after initial compromise. “a domain with no legitimate business purpose” is why proof of “periodic communications as possible command-and-control” matters here.

C:

For assessment and interpretation, contrasting “Recognize DNS tunneling or encoded” with “a domain with no legitimate business purpose”, high-entropy labels and repeated queries can carry data or commands through DNS. “beacon-like periodic communications as possible command-and-control” cannot be inferred from that “a domain with no legitimate business purpose” finding.

D:

For assessment and interpretation, contrasting “Recognize lateral reconnaissance rather than” with “a domain with no legitimate business purpose”, a sweep across peers and ports signals discovery for follow-on compromise. Only “periodic communications as possible command-and-control” would test the “a domain with no legitimate business purpose” condition.

E:

For assessment and interpretation, contrasting “Recognize potential malware-assisted collection and” with “a domain with no legitimate business purpose”, archiving followed by unexplained upload is more suspicious than either event alone. The “a domain with no legitimate business purpose” report requires a finding about “beacon-like periodic communications as possible”.

Question 501

A malware alert occurs just after a trusted software package was updated by an internal repository. What engineering or process change closes the original failure path?

  1. Clean or replace affected media and harden execution controls
  2. Rotate affected credentials and repair the account-provisioning weakness
  3. Rebuild packages from verified source and restore trusted signing controls
  4. Sanitize restored data and harden macro and attachment execution policy

Explanation

Correct Answer

C:

For eradication and systemic correction involving “Rebuild packages from verified source” and the report “package was updated by an internal repository”, a clean release pipeline removes the contaminated distribution path. “Suspend rollout and isolate affected update recipients” is interim risk reduction.

Incorrect Answers

A:

For eradication and systemic correction, contrasting “Clean or replace affected media” with “package was updated by an internal repository”, root cause includes the contaminated media and permissive autorun policy. “package was updated by an internal repository” gives a different evidentiary target: “from verified source and restore trusted signing”.

B:

For eradication and systemic correction, contrasting “Rotate affected credentials and repair” with “package was updated by an internal repository”, removing one key is insufficient if the attacker can write new ones. The incident detail “package was updated by an internal repository” still calls for “source and restore trusted signing controls”.

D:

For eradication and systemic correction, contrasting “Sanitize restored data and harden” with “package was updated by an internal repository”, data recovery must exclude active malicious content and unsafe execution defaults. Against “package was updated by an internal repository”, this does not establish “verified source and restore trusted signing controls”.

Question 502

A manager accuses an employee of theft based only on a DLP alert generated during an approved migration. What should be changed to prevent recurrence rather than only quiet alerts?

  1. Tune DLP correlations using sanctioned transfer windows and approval IDs
  2. Automate HR-driven deprovisioning with exception and completion checks
  3. Require entitlement recertification at every role transfer
  4. Establish confidential whistleblower protection and impartial case review

Explanation

Correct Answer

A:

For eradication and systemic correction involving “Tune DLP correlations using sanctioned” and the report “DLP alert generated during an approved migration”, contextual rules reduce false accusations without ignoring unauthorized copies. “Avoid disciplinary escalation until the security event is validated” is the interim response.

Incorrect Answers

B:

For eradication and systemic correction, contrasting “Automate HR-driven deprovisioning with exception” with “DLP alert generated during an approved migration”, authoritative lifecycle signals reduce missed revocations. For the “DLP alert generated during an approved migration” observation, “using sanctioned transfer windows and approval IDs” remains open.

C:

For eradication and systemic correction, contrasting “Require entitlement recertification at every” with “DLP alert generated during an approved migration”, joiner-mover-leaver controls must handle internal movers, not only departures. The “Tune DLP correlations using” requirement follows from “DLP alert generated during an approved migration”.

D:

For eradication and systemic correction, contrasting “Establish confidential whistleblower protection and” with “DLP alert generated during an approved migration”, independent oversight balances risk detection with due process. “sanctioned transfer windows and approval IDs” remains unverified against the reported “DLP alert generated during an approved migration”.

Question 503

An account portal lets users change the email field in a privileged update request and silently apply changes to another account. What should the team verify after implementing the corrective action?

  1. Verify forbidden fields and other users' records remain unchanged under tests
  2. Test denied admin calls from lower-privilege users and allowed calls from admins
  3. Test second redemption fails and account recovery notifications are accurate
  4. Run cross-user and cross-tenant negative tests before reopening

Explanation

Correct Answer

A:

For recovery and closure validation involving “Verify forbidden fields and other” and the report “and silently apply changes to another account”, a fix requires both property and ownership boundaries. “Allowlist writable fields and enforce object-level access checks” is the correction whose effectiveness is being retested.

Incorrect Answers

B:

For recovery and closure validation, contrasting “Test denied admin calls from” with “and silently apply changes to another account”, negative and positive tests prove the intended permission boundary. Here, “other users records remain unchanged under tests” must account for “and silently apply changes to another account”.

C:

For recovery and closure validation, contrasting “Test second redemption fails and” with “and silently apply changes to another account”, verification focuses on replay rejection and user visibility. “and silently apply changes to another account” needs a more direct result for “forbidden fields and other users records”.

D:

No record should be accessible solely by guessing its identifier. The comparison turns on “and silently apply changes to another account” versus “other users records remain unchanged under”.

Question 504

Google Cloud Audit Logs show an unauthorized IAM policy update affecting a sensitive project. Which explanation of the security concern most directly fits the evidence?

  1. Recognize ephemeral logging loss in orchestrated workloads
  2. Recognize possible malicious deployment or secret misuse in serverless execution
  3. Recognize a potentially compromised workload rather than solely a firewall fault
  4. Recognize administrative privilege change captured by audit events

Explanation

Correct Answer

D:

For assessment and interpretation involving “Recognize administrative privilege change captured” and the report “IAM policy update affecting a sensitive project”, a policy mutation can grant resource access without touching application code. “Preserve Admin Activity records and the before-and-after IAM bindings” is a separate source of incident context.

Incorrect Answers

A:

For assessment and interpretation, contrasting “Recognize ephemeral logging loss in” with “IAM policy update affecting a sensitive project”, container replacement can discard local context needed to trace an exploit. “administrative privilege change captured by audit events” cannot be inferred from that “IAM policy update affecting a sensitive project” finding.

B:

For assessment and interpretation, contrasting “Recognize possible malicious deployment or” with “IAM policy update affecting a sensitive project”, short-lived functions can leak data without leaving persistent VM artifacts. Only “privilege change captured by audit events” would test the “IAM policy update affecting a sensitive project” condition.

C:

Outbound command traffic can originate from changed guest software. The “IAM policy update affecting a sensitive project” report requires a finding about “administrative privilege change captured by audit events”.

Question 505

A Linux host no longer shows malware processes but a hidden unauthorized SSH key remains in an account. Which record set is most directly useful for verifying what happened?

  1. Collect account key history, login logs and file modification metadata
  2. Preserve the document, macro indicators and cloud sync event history
  3. Preserve device connection history, worm samples and kiosk task logs
  4. Collect script behavior, execution parents and multiple sample hashes

Explanation

Correct Answer

A:

For evidence selection and preservation involving “Collect account key history, login” and the report “unauthorized SSH key remains in an account”, this evidence connects persistence to actual access and timing. “Disable the unauthorized key and restrict the account pending review” is the specific follow-up action.

Incorrect Answers

B:

For evidence selection and preservation, contrasting “Preserve the document, macro indicators” with “unauthorized SSH key remains in an account”, the payload and synchronization path explain why infection returned. Against “unauthorized SSH key remains in an account”, this does not establish “login logs and file modification”.

C:

For evidence selection and preservation, contrasting “Preserve device connection history, worm” with “unauthorized SSH key remains in an account”, removable-media telemetry can identify the recurrent source. For “Collect account key”, the case record must resolve “unauthorized SSH key remains in an account”.

D:

For evidence selection and preservation, contrasting “Collect script behavior, execution parents” with “unauthorized SSH key remains in an account”, behavioral commonalities support broader detection than one fixed indicator. “unauthorized SSH key remains in an account” is why proof of “login logs and file modification metadata” matters here.

Question 506

A customer-impact incident has strong technical evidence but no agreed definition of when to notify the service provider. Which preventive correction targets the problem at its source?

  1. Maintain jurisdiction-specific notification decision trees under legal review
  2. Create a stakeholder matrix with approval and update responsibilities
  3. Add an impact and risk-acceptance section to the reporting template
  4. Build approved evidence-sharing agreements and minimization procedures
  5. Add vendor-notification triggers to the incident response runbook

Explanation

Correct Answer

E:

For eradication and systemic correction involving “Add vendor-notification triggers to the” and the report “of when to notify the service provider”, embedding contract conditions reduces dependence on individual analyst memory. “Notify the contract owner and provider through the designated secure channel” is interim risk reduction.

Incorrect Answers

A:

For eradication and systemic correction, contrasting “Maintain jurisdiction-specific notification decision trees” with “of when to notify the service provider”, documented, current guidance reduces missed deadlines and inconsistent choices. The “vendor-notification triggers to the incident response runbook” requirement follows from “of when to notify the service provider”.

B:

For eradication and systemic correction, contrasting “Create a stakeholder matrix with” with “of when to notify the service provider”, a repeatable notification plan avoids competing or premature public statements. “triggers to the incident response runbook” remains unverified against the reported “of when to notify the service provider”.

C:

For eradication and systemic correction, contrasting “Add an impact and risk-acceptance” with “of when to notify the service provider”, a structured summary makes decisions explicit rather than buried in log screenshots. For “of when to notify the service provider”, the missing check concerns “vendor-notification triggers to the incident response runbook”.

D:

For eradication and systemic correction, contrasting “Build approved evidence-sharing agreements and” with “of when to notify the service provider”, clear handling rules govern recipients, retention and onward disclosure. “of when to notify the service provider” gives a different evidentiary target: “vendor-notification triggers to the incident response”.

Question 507

An IT engineer uses a shared administrator account, so investigators cannot tell who changed payroll permissions. What records would most clearly support validation of the reported activity?

  1. Preserve role-assignment changes, mailbox access events and request history
  2. Collect grant records, use history and incident-linked approval details
  3. Preserve privileged session recordings, access gateway logs and shift rosters
  4. Preserve database audit events, approval records and destination metadata

Explanation

Correct Answer

C:

For evidence selection and preservation involving “Preserve privileged session recordings, access” and the report “investigators cannot tell who changed payroll permissions”, supplemental context may attribute the session despite shared credentials. “Suspend unmanaged shared access and move urgent work to named accounts” is a later protective decision.

Incorrect Answers

A:

For evidence selection and preservation, contrasting “Preserve role-assignment changes, mailbox access” with “investigators cannot tell who changed payroll permissions”, the evidence connects the privilege change to subsequent use. “investigators cannot tell who changed payroll permissions” needs a more direct result for “gateway logs and shift”.

B:

For evidence selection and preservation, contrasting “Collect grant records, use history” with “investigators cannot tell who changed payroll permissions”, reviewers must establish whether the role was used beyond its authorized purpose. The comparison turns on “investigators cannot tell who changed payroll permissions” versus “access gateway logs and shift rosters”.

D:

For evidence selection and preservation, contrasting “Preserve database audit events, approval” with “investigators cannot tell who changed payroll permissions”, comparison with authorized work distinguishes misuse from emergency operations. “recordings access gateway logs and shift” is the criterion not satisfied for “investigators cannot tell who changed payroll permissions”.

Question 508

An attacker alters the body of a signed email after it leaves the sending service. What records would most clearly support validation of the reported activity?

  1. Preserve complete headers including Return-Path and Authentication-Results
  2. Inspect DKIM-Signature fields, body hash and verifier results
  3. Collect headers and sender-domain alignment results for affected mail
  4. Inspect the evaluated SPF path and DNS lookup outcomes

Explanation

Correct Answer

B:

For evidence selection and preservation involving “Inspect DKIM-Signature fields, body hash” and the report “email after it leaves the sending service”, cryptographic verification shows whether signed content survived transit intact. “Hold suspicious messages pending authenticity assessment” is a later protective decision.

Incorrect Answers

A:

For evidence selection and preservation, contrasting “Preserve complete headers including Return-Path” with “email after it leaves the sending service”, envelope and authentication metadata reveal which domains and IPs were actually checked. The “email after it leaves the sending service” report requires a finding about “Inspect DKIM-Signature fields body hash”.

C:

For evidence selection and preservation, contrasting “Collect headers and sender-domain alignment” with “email after it leaves the sending service”, the details distinguish routing problems from SPF, DKIM or DMARC misconfiguration. For this “email after it leaves the sending service” event, “Inspect DKIM-Signature fields body hash and” is still outstanding.

D:

For evidence selection and preservation, contrasting “Inspect the evaluated SPF path” with “email after it leaves the sending service”, actual DNS resolution exposes excessive lookups or broken referenced records. “email after it leaves the sending service” is not evaluated through the “fields body hash and verifier results” requirement.

Question 509

A malicious browser extension survives browser restarts and modifies corporate portal sessions. Which information should be retained before the incident history is lost?

  1. Preserve scheduled tasks, startup keys and process creation events
  2. Capture memory mappings, loaded modules and process/network lineage
  3. Export configuration history, account events and management access logs
  4. Record extension IDs, granted permissions, install source and browser logs

Explanation

Correct Answer

D:

For evidence selection and preservation involving “Record extension IDs, granted permissions” and the report “browser restarts and modifies corporate portal sessions”, the extension metadata documents both capability and deployment route. “Disable the extension across managed profiles and revoke at-risk sessions” is the specific follow-up action.

Incorrect Answers

A:

For evidence selection and preservation, contrasting “Preserve scheduled tasks, startup keys” with “browser restarts and modifies corporate portal sessions”, configuration plus execution traces identify the trigger and executable. For “extension IDs granted permissions install”, the case record must resolve “browser restarts and modifies corporate portal sessions”.

B:

For evidence selection and preservation, contrasting “Capture memory mappings, loaded modules” with “browser restarts and modifies corporate portal sessions”, memory and EDR telemetry expose code that filesystem scans may miss. “browser restarts and modifies corporate portal sessions” is why proof of “granted permissions install source and browser” matters here.

C:

For evidence selection and preservation, contrasting “Export configuration history, account events” with “browser restarts and modifies corporate portal sessions”, correlating changes with sessions helps identify the origin of re-creation. The collected facts can inform the separate handling decision to restrict management access to a trusted recovery network and rotate secrets.

Question 510

An API accepts access tokens signed for a different service because it checks only that the signature is valid. What observable outcome best supports an incident closure decision?

  1. Confirm the same token is rejected after logout across all API nodes
  2. Test denied admin calls from lower-privilege users and allowed calls from admins
  3. Test well-signed wrong-audience tokens are consistently rejected
  4. Run cross-user and cross-tenant negative tests before reopening

Explanation

Correct Answer

C:

Security must not depend solely on the signature check. “Enforce issuer, audience, expiry and signing algorithm checks” is the permanent measure linked to the closure evidence.

Incorrect Answers

A:

For recovery and closure validation, contrasting “Confirm the same token is” with “checks only that the signature is valid”, a front-end sign-out screen is not sufficient proof. For “checks only that the signature is valid”, the missing check concerns “Test well-signed wrong-audience tokens”.

B:

For recovery and closure validation, contrasting “Test denied admin calls from” with “checks only that the signature is valid”, negative and positive tests prove the intended permission boundary. “checks only that the signature is valid” gives a different evidentiary target: “well-signed wrong-audience tokens are consistently rejected”.

D:

For recovery and closure validation, contrasting “Run cross-user and cross-tenant negative” with “checks only that the signature is valid”, no record should be accessible solely by guessing its identifier. “wrong-audience tokens are consistently rejected” addresses a gap left by the “checks only that the signature is valid” observation.

EC-Council Certified Incident Handler (212-89) Practice Tests