Topic lessonTopic: AWS security services explained: prevention, findings and response
AWS security services explained: prevention, findings and response
Combine prevention that reduces risk, detection that identifies signs of trouble, and response that investigates and limits impact. Compare four representative AWS services using a fictional reporting server. Keep the presence of a finding separate from evidence that compromise or recovery has been established.
Choose functions and evidence for prevention, detection and response; explain what to pass to the responsible team without treating a finding as proof of compromise or completed remediation.
Know that AWS resources support applications and data, and permissions control operations on them. No AWS account or key is needed. Read fictional summaries without submitting logs, credentials or real security data.
Prevention, detection and response answer different questions
Prevention reduces the likelihood or impact of problems, for example by withholding unnecessary permissions. Detection observes activity or configuration and identifies signs of trouble. Response investigates those signs and their impact, then has authorized people take appropriate protective or recovery actions and verify the outcome. Prevention does not remove the need for detection and response.
An Amazon GuardDuty finding, as used in this lesson, reports a potential security issue. An incident involves a violation, or an imminent threat of violating security policies or practices. A generated finding differs from a substantiated conclusion about compromise, damage or cause. Handle suspicions under the organization's response procedures while keeping unconfirmed conclusions unconfirmed.
A fictional reporting server receives a suspicious-activity report
A fictional organization processes internal reports on server R. An analyst receives these three summaries about the same R in learning account A and Region A. A Region is a geographical area for resources. F1, T1 and C1 are reading examples, not reproductions of product screens or real logs.
| Item | What this example supplies | What it does not establish alone |
|---|---|---|
| F1: threat finding | Signs of suspicious activity involving server R during the period. | Compromise, impact scope or completed response. |
| T1: activity record | One request to change R's traffic configuration was denied during the same period. | Outcomes of other requests or a causal link to F1. |
| C1: configuration records | The supplied configuration items for R show no difference at the two compared points. | Unrecorded state, intervening or later changes, or internal application state. |
Connect controls, evidence, threat indicators and response
AWS Identity and Access Management (IAM) is a representative access-control service. AWS CloudTrail records activity, AWS Config provides resource configuration and history, and Amazon GuardDuty detects potential threats. They provide different information. These four illustrate roles; they are not an inventory of every AWS security service.
- Prevent: limit access → Detect: assess signsKeep observing even when controls exist
- Detect: assess signs → Respond: act safelyInvestigate indicators; owners decide on action
- Prevent: limit access
- Use controls such as IAM to consider who may do what.
- Detect: assess signs
- Distinguish GuardDuty findings from activity and configuration evidence.
- Respond: act safely
- Check authority, evidence and impact; verify the result of any action.
The diagram connects functions. Keep observing despite access controls, investigate indicators and bring them into an owner's response decision. Arrows do not specify log delivery, network paths or configured automatic remediation. Real work is not a one-pass sequence: responding can include revisiting permissions.
| Representative function | Question it supports | Keep separate |
|---|---|---|
| IAM: access control | Which identity may perform which actions on which resources? | Sign-in differs from permission for an operation. Permission does not prove that activity was legitimate. |
| CloudTrail: activity records | Which operation was requested and which outcome was recorded? | An operation name is not proof of success or cause. Check event categories, period and destination. |
| Config: configuration and evaluation | What configuration was recorded? Does it meet selected criteria? | Recording, rule evaluation and remediation outcomes are different; recording and criteria have scope. |
| GuardDuty: threat detection | Which potential security issue was identified? | A finding alone does not prove compromise or recovery. Check subject, features and data-source conditions. |
Do not assign each service to exactly one stage. Activity and configuration records can support both discovering an issue and investigating a response. Combining Config rule evaluation with remediation still requires separate checks of actions, permissions and results. A displayed feature name does not establish your organization's enablement, collection scope, costs or success.
Change a condition and choose the next conclusion
Choose an option to see the result and explanation.
Prepare a useful handoff, then choose further reading
- Retain the necessary subject, period, sources and observed facts. Do not submit real data or secrets to this site.
- Separate hypotheses, impact and collection gaps from facts when handing over. Assess urgency under your organization's procedures.
- If a change is needed, review authority, business impact, evidence preservation and a way to recover.
- Record actions and outcomes, business/data recovery and remaining unknowns. Closing a notification alone does not resolve the issue.
Continue to IAM for permissions, CloudTrail for activity records, or Config for configuration and evaluation. Use the related lessons at the end to revisit responsibility and investigation when needed.
Check, then explain in your own words
- State the prevention, detection and response questions for server R.
- Separate what F1's indicator, T1's denial and C1's unchanged values establish from what remains unknown.
- Explain the next decision using evidence, ownership and action results rather than feature names or notifications alone.
Check your understanding: Someone says, 'we have findings and records.' What should you check before concluding compromise or recovery?
Align subject, time, content and collection scope; separate observations, hypotheses and unknowns. Establish the responsible team's investigation or action and verify its results.
A potential-issue report, activity/configuration records, and actual compromise, impact or recovery are different facts.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- What is IAM?Checked:
Scope and conditionsAuthentication, authorization and access control; permission is not proof of legitimate activity or absence of compromise. Documentation review, no configuration or AWS execution.
Used in this lessonPrevention, detection and response answer different questions Connect controls, evidence, threat indicators and response
- What Is AWS CloudTrail?Checked:
Scope and conditionsActivity-event role and differing recording scopes; not complete coverage or causation proof. Detailed Insights features are out of scope. Documentation only.
Used in this lessonConnect controls, evidence, threat indicators and response
- What Is AWS Config?Checked:
Scope and conditionsResource configuration, relationships, history and selected-rule evaluation. Recording scope/frequency remain conditions; no universal history or security guarantee. Documentation only.
Used in this lessonConnect controls, evidence, threat indicators and response Change a condition and choose the next conclusion
- What is Amazon GuardDuty?Checked:
Scope and conditionsPotential-threat detection; feature, protection-plan and data-source conditions vary. No claims of complete detection, default enablement or fixed pricing. New/preview feature catalog omitted. Documentation only.
Used in this lessonPrevention, detection and response answer different questions Connect controls, evidence, threat indicators and response Change a condition and choose the next conclusion
Scope and conditionsFindings represent potential issues. Samples differ from resource-deploying testers; neither is executed. F1 is not an official finding type or JSON reproduction. Documentation only.
Used in this lessonPrevention, detection and response answer different questions Connect controls, evidence, threat indicators and response Change a condition and choose the next conclusion
- Finding detailsChecked:
Scope and conditionsFinding details vary by type; examine subject, account/Region/resource and timestamps. Do not conflate actor/target or timestamp meanings, and do not request real data. Documentation only.
Used in this lessonChange a condition and choose the next conclusion
Scope and conditionsInvestigation/response depends on finding subject and type. No universal deletion recipe or recovery guarantee. The teaching checklist is editorial synthesis, not a product runbook or authorization.
Used in this lessonPrevention, detection and response answer different questions Connect controls, evidence, threat indicators and response Change a condition and choose the next conclusion
Scope and conditionsConfig Rules remediation uses separately associated actions such as SSM Automation documents. Evaluation differs from action completion and recovery. Actual setup, Region, permissions and costs unverified.
Used in this lessonConnect controls, evidence, threat indicators and response Change a condition and choose the next conclusion
Scope and conditionsAWS/customer duties depend on service and use. Organizational ownership and completion do not follow automatically. No compliance or deployment-security assessment performed.
Used in this lessonPrevention, detection and response answer different questions
Scope and conditionsIncident terminology covers policy/practice violations or imminent threats. Used to distinguish findings from established compromise, not to prescribe or certify adoption of the AWS Security Incident Response product.
Used in this lessonPrevention, detection and response answer different questions