Skip to content

opensite-ai/opensite-skills / aws-security

aws-security

Verified

Covers AWS security services and workflows — Security Hub V2 (OCSF) findings, connectors, aggregators, automation rules, and security posture summaries; Security Hub CSPM (V1/ASFF) controls and compliance standards; GuardDuty threat findings; Inspector vulnerability findings; Macie sensitive data findings; Detective investigation; and Security Lake configuration and data aggregation. Applicable when questions involve security posture, Exposure findings, CSPM failed controls, threat findings, vulnerability findings, sensitive data findings, automation rules, or cross-service security configuration across AWS environments. Procedures use standard AWS CLI syntax and work with or without the AWS MCP server.

references/detective.md

View on GitHub
# Detective

- **Docs**: https://docs.aws.amazon.com/detective/latest/userguide/
- **Docs (llms.txt)**: https://docs.aws.amazon.com/detective/latest/userguide/llms.txt

Amazon Detective helps investigate security findings by building behavior graphs from CloudTrail management events, VPC Flow Logs, GuardDuty findings, EKS audit logs, and Security Hub CSPM findings. It does not generate findings — it provides investigation context through entity profiles, finding groups, and automated investigations. Detective does NOT support S3 data events. Detective uses AWS Security Finding Format (ASFF) for ingestion. It does not produce findings — it produces investigations.

## Data Sources

```mermaid
graph LR
    CT[CloudTrail Mgmt Events] --> DET[Detective]
    VPC[VPC Flow Logs] --> DET
    GDF[GuardDuty Findings] --> DET
    EKS[EKS Audit Logs] --> DET
    SHF[Security Hub CSPM Findings] --> DET
    DET -->|builds| BG[Behavior Graphs / Investigations]
```

## Read-Only APIs

| API | Purpose |
|-----|---------|
| `detective:ListGraphs` | Discover behavior graphs |
| `detective:ListDatasourcePackages` | Check enabled data source packages |
| `detective:ListMembers` | List graph members |
| `detective:ListInvitations` | Check pending invitations |
| `detective:ListOrganizationAdminAccounts` | Identify delegated admin |
| `detective:DescribeOrganizationConfiguration` | Get org auto-enable settings |
| `detective:ListInvestigations` | List investigations with filters |
| `detective:GetInvestigation` | Get investigation details |
| `detective:ListIndicators` | List indicators for an investigation |

## Severity Scoring

Detective investigations use a severity score:

| Level | Description |
|-------|-------------|
| INFORMATIONAL | Investigation found no notable indicators |
| LOW | Minor anomalies detected |
| MEDIUM | Notable behavioral deviations |
| HIGH | Significant threat indicators |
| CRITICAL | Strong evidence of compromise |

**Key notes:**

- Investigation severity is based on the combination and weight of indicators found
- Indicator types: TTP_OBSERVED, IMPOSSIBLE_TRAVEL, FLAGGED_IP_ADDRESS, NEW_GEOLOCATION, NEW_ASO, NEW_USER_AGENT, RELATED_FINDING, RELATED_FINDING_GROUP
- Detective does not generate findings — it produces investigations and finding groups from ingested data

**Documentation:** https://docs.aws.amazon.com/detective/latest/userguide/investigations-report.html

## Service Notes

- **Detective**: Ingests Security Hub CSPM findings in ASFF format but produces investigations in its own proprietary format. Does NOT support S3 data events. Focuses on investigations and finding groups, not findings.

## Output Sensitivity

Detective investigation details (`GetInvestigation`, `ListIndicators`) contain:

- AWS account IDs and IAM principal ARNs under investigation
- IP addresses flagged as suspicious (FLAGGED_IP_ADDRESS indicators)
- Geolocation data (NEW_GEOLOCATION, IMPOSSIBLE_TRAVEL indicators)
- User agent strings and ASN details
- Related GuardDuty finding IDs and Security Hub finding references

Present investigation status/severity summary first. Offer full indicator details on request.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall