CISSP - Security Operations - Section 7.2

Conduct logging and monitoring activities including IDS/IPS, SIEM, SOAR, threat intelligence, UEBA, and continuous monitoring.

Configure and operate SIEM, SOAR, IDS/IPS, and UEBA platforms in conjunction with threat intelligence feeds to support continuous monitoring of the security posture. Distinguish between detection capabilities so that alert triage correctly separates genuine threats from tuning noise.

SIEMSOARIDS/IPSthreat intelligenceUEBAcontinuous monitoring

Practice question for this objective

Free sampleSecurity Operationshard

A healthcare provider has just stood up a managed SIEM, an IDS/IPS at the perimeter, and a commercial threat-intelligence subscription. Six weeks in, the SOC reports that high-confidence intelligence indicators are arriving by email but are not influencing detections or blocking decisions in any consistent way. The CISO asks the security architect for the BEST structural fix. Which option should the architect recommend?

  • ADirect the SOC to manually review the intelligence emails each morning and raise change requests to add the highest-confidence indicators to the IDS/IPS block list within 24 hours.
  • BEstablish a threat-intelligence platform that normalises, deduplicates, and scores indicators, then pushes them via API into the SIEM correlation engine and the IDS/IPS, with a documented confidence-to-action policy. Correct
  • CReplace the commercial subscription with a broader open-source intelligence feed so the SOC has more indicators to choose from when writing detection content.
  • DAdd a SOAR platform that ingests the intelligence emails, parses indicators, and auto-creates SIEM correlation rules and IDS/IPS block entries based on the email's stated severity.
Integrate threat intelligence into detection and prevention through a normalising platform and an explicit confidence-to-action policy. Operationalising threat intelligence requires more than a subscription. Indicators arrive in mixed formats and varying confidence, and need to be normalised (often via STIX/TAXII), deduplicated across feeds, and scored before any sensor acts on them. A threat-intelligence platform sits between the feeds and the SIEM, IDS/IPS, and SOAR, providing the API-driven integration and the audit trail that justifies why a given indicator triggered a detection or block. A documented confidence-to-action policy then governs which scores warrant alerting, blocking, or hunting.

Why A is wrong: Manual review is slow, inconsistent, and dependent on the diligence of whoever opens the inbox. It also separates the intelligence from the detection context, so analysts cannot tell which alert came from which indicator, making after-action review difficult.

Why B is correct: Correct. A threat-intelligence platform provides the missing middle layer: normalising STIX/TAXII content, deduplicating across sources, scoring confidence, and feeding the SIEM and IDS/IPS through machine-to-machine integration. Coupled with a confidence-to-action policy, it converts intelligence into consistent detection and blocking decisions.

Why C is wrong: Switching feeds does not address the integration gap. More indicators without an ingestion and scoring pipeline simply increases noise, and open-source feeds typically carry lower fidelity than the commercial source being replaced.

Why D is wrong: SOAR can automate response but is the wrong tool for managing intelligence quality. Parsing emails of variable format is fragile, severity in vendor emails is not normalised, and auto-creating rules without confidence scoring or deduplication risks blocking legitimate traffic.

See more CISSP practice questions, answers explained.

More in this domain

Back to all Security Operations objectives, or the CISSP cert hub.

Examworthy is not affiliated with or endorsed by ISC2. Original, blueprint-aligned practice material only.