Cloud concept · Updated

False Positives - False positives are detections that incorrectly indicate a security threat or policy violation when the condition being tested is absent.

In short

Security tools identify patterns and conditions that require validation, not automatic acceptance as confirmed incidents. Distinguishing false positives from genuine threats and accurately detected but authorized activity helps responders assess scope and impact without wasting investigation time or disrupting legitimate workloads.

Cloud Concepts Hub →

6 key aspects of False Positives

Reliable false-positive handling combines corroborating evidence, precise classification, impact assessment, and narrowly controlled tuning without sacrificing threat visibility.

01
Evidence-based validation

Treat a security finding as a claim to test against audit records, workload telemetry, configuration state, and operational context. Severity and anomaly scores support prioritization but do not independently establish compromise.

02
Accurate finding disposition

Distinguish an incorrect detection from accurately detected authorized behavior, a genuine policy violation, and an unresolved finding. Record the reasoning so future responders can understand and reassess the decision.

03
Scope and impact assessment

Identify affected identities, resources, accounts, Regions, and time periods, then determine which actions succeeded. Do not equate attempted access with successful access or successful access with confirmed exfiltration.

04
Telemetry-aware conclusions

Check whether relevant logs were enabled, retained, and delivered before interpreting missing evidence. Visibility gaps should reduce confidence rather than justify automatically closing an alert.

05
Controlled suppression

Suppress only well-understood conditions using narrowly scoped criteria and documented ownership. Review exceptions periodically because authorization, resource sensitivity, and attacker behavior can change.

06
Balanced detection quality

Evaluate reductions in alert noise alongside the risk of missed threats. Distinguish the false-positive rate from the proportion of generated alerts that are false.

Cloud services for False Positives

GuardDuty generates threat findings, while Security Hub provides a central place to review findings and track investigation decisions. CloudTrail supplies API audit evidence that helps establish which identities performed which operations and whether those requests succeeded. Detective adds relationship and behavioral context for investigating connected activity. Together, these services support a validation workflow rather than an automatic verdict: inspect the claim, corroborate it, assess affected resources and impact, and document the disposition. Apply suppression only after validation, and keep telemetry coverage gaps visible so an absence of evidence is not mistaken for proof of benign activity.

Amazon GuardDutyAmazon GuardDuty

GuardDuty findings identify suspicious activity that responders must validate using the finding details and supporting telemetry. Suppression rules can automatically archive matching findings for reviewed conditions, but archiving does not contain a threat or remediate its cause.

AWS Security HubAWS Security Hub

Security Hub centralizes security findings and supports investigation workflows. Where finding workflow status is supported, SUPPRESSED records a decision not to act on a finding; it does not establish that the underlying condition is fixed or that the original detection was incorrect.

AWS CloudTrailAWS CloudTrail

CloudTrail provides audit evidence for validating identities, API actions, request timing, and outcomes. Investigators must check event coverage because data events require explicit configuration, and event history is not a complete record of every resource operation.

Amazon DetectiveAmazon Detective

Detective helps investigators examine relationships and activity involving identities, IP addresses, and resources. Its contextual views support testing whether a finding fits expected behavior and identifying related activity that could expand an incident's scope.

False Positives exam questions

Real practice exam questions on False Positives, with the correct answer and its explanation. Answer them with every option in the exam simulator.

DOP-C02

A company delivers AWS CloudTrail sign-in events to Amazon CloudWatch Logs. A metric filter matches events whose eventName is ConsoleLogin and whose userIdentity.type is Root. A CloudWatch alarm notifies the security team whenever the metric count is at least 1 in a one-minute period. The runbook describes each notification as a successful root-user sign-in.

Investigators determine that several notifications correspond to failed authentication attempts. These events contain responseElements.ConsoleLogin set to Failure and an errorMessage, but no errorCode field. Some attempts originate from a corporate NAT address that is also used for legitimate administration.

Security policy requires notification of every successful root-user console sign-in, including approved sign-ins, regardless of source address or MFA use. Failed attempts must remain available for investigation but must not trigger this successful-sign-in alarm.

Which change should a DevOps engineer make?

Show answerCORRECT ANSWER

Update the metric filter to require eventSource to equal signin.amazonaws.com, eventName to equal ConsoleLogin, userIdentity.type to equal Root, and responseElements.ConsoleLogin to equal Success. Keep the existing alarm threshold and retain all original log events.

The current filter detects root sign-in attempts, not successful root sign-ins. Requiring the explicit successful authentication outcome eliminates the false reports of success while preserving notifications for successful sign-ins from any address and with any MFA status. Metric filtering does not remove the failed attempts from the log group.

Practice False Positives in a full exam

Questions on False Positives in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is False Positives

3 min read

A false positive occurs when a detection reports a condition that is not actually present. In cloud security, this might be an intrusion alert caused by legitimate administrative traffic or a sensitive-data finding triggered by synthetic test records. A finding is an investigative lead: its severity indicates prioritization, but does not prove that an attacker succeeded, that credentials were compromised, or that data was exposed.

Responders should distinguish false positives from benign true positives. If a detector correctly identifies port scanning and the scanner is an approved security-testing system, the observed behavior is real but authorized. That is often classified as a benign true positive rather than a detection error. Similarly, a publicly accessible storage resource can represent a genuine configuration finding even when its owner intended public access. Whether an exception is appropriate depends on the applicable policy and the resource's contents, not merely on the owner's explanation.

Validation starts with the finding's actual claim. Examine the affected account, Region, resource, principal, source address, event times, detection type, and supporting evidence. Determine whether the finding describes an attempted action, a successful operation, an exposed configuration, or behavior that differs from a baseline. Separate facts established by telemetry from assumptions introduced during triage.

Correlate the finding with independent evidence. Cloud audit records can identify API operations, role sessions, source addresses, and request outcomes. Network flow records can help establish communication patterns, while application logs, identity-provider records, configuration history, and approved change records provide additional context. Normalize timestamps and account for temporary credentials, shared egress addresses, proxies, and automation. An unfamiliar IP address alone does not establish compromise, and a familiar address does not prove that an action was authorized.

For example, an unusual API activity finding might coincide with a deployment pipeline using a newly introduced role session. Validate the session issuer, deployment records, requested operations, and affected resources before dismissing the finding. If the activity instead includes unexpected permission changes and successful access to sensitive objects, expand the investigation across related sessions, accounts, and time periods. Establish what actions succeeded, what resources changed, and what data was accessed; a suspicious request by itself does not establish data exfiltration.

Missing evidence requires caution. Some cloud audit data events and workload logs require explicit configuration, and retention or delivery delays can limit visibility. The absence of a matching log entry is not sufficient to declare a false positive. Record these gaps and retain an unresolved disposition when available evidence cannot support a conclusion. If evidence indicates active compromise, proportionate containment may be necessary before the investigation is complete.

After validation, document the disposition, supporting evidence, scope, impact, and reasoning. Narrowly scoped suppression rules can reduce repeated alerts for verified conditions, but suppression does not fix a vulnerability, revoke credentials, or make the underlying activity safe. Give exceptions an owner and review date, and reassess them when workloads or threat conditions change. Avoid broadly suppressing an entire identity, network range, or finding category because one alert was harmless.

Detection tuning involves a trade-off: stricter matching can reduce false positives while increasing false negatives, meaning real threats are missed. Measure both investigative workload and detection coverage. The false-positive rate is false positives divided by all actual negative cases; it is not the percentage of alerts judged false. That latter measure is the false discovery proportion. Keeping these measures distinct prevents misleading claims about detection quality and supports safer automation decisions.

Learn False Positives in lessons

2 short lessons on False Positives in 2 certification courses.

Open the lessons