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/macie.md

View on GitHub
# Macie

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

Amazon Macie is a data security service that uses machine learning and pattern matching to discover and classify sensitive data stored in Amazon S3. It identifies PII, financial data, credentials, and other sensitive content, and assesses S3 bucket access configurations. Findings are in Macie's proprietary JSON format and are also sent to Security Hub in OCSF format.

## Data Sources

Macie analyzes:

- S3 bucket inventory and access configurations (automated)
- S3 object content via classification jobs or automated sensitive data discovery
- Macie scans objects in [supported S3 storage classes](https://docs.aws.amazon.com/macie/latest/user/discovery-supported-storage.html) only (not all classes are supported; consult the linked documentation)

## Read-Only APIs

| API | Purpose |
|-----|---------|
| `macie2:GetMacieSession` | Check Macie enablement status |
| `macie2:GetAutomatedDiscoveryConfiguration` | Check automated discovery settings |
| `macie2:ListClassificationJobs` | List classification jobs |
| `macie2:DescribeClassificationJob` | Get job details |
| `macie2:GetFindingsPublicationConfiguration` | Get finding publication settings |
| `macie2:GetClassificationExportConfiguration` | Get classification export destination (S3 bucket) |
| `macie2:ListAllowLists` | List allow lists |
| `macie2:GetRevealConfiguration` | Get reveal configuration status |
| `macie2:GetUsageTotals` | Get usage and cost estimates |
| `macie2:ListOrganizationAdminAccounts` | Identify delegated admin |
| `macie2:DescribeOrganizationConfiguration` | Get org auto-enable settings |
| `macie2:ListMembers` | List member accounts |
| `macie2:GetFindingStatistics` | Get aggregated finding statistics |
| `macie2:ListFindings` | List finding IDs |
| `macie2:GetFindings` | Get finding details (batch, max 50) |
| `macie2:ListResourceProfileDetections` | List resource profile detections |
| `macie2:GetSensitiveDataOccurrencesAvailability` | Check if sensitive data samples available |

## Severity Scoring

Macie assigns severity (1-3 scale) based on **sensitive data type** and context, not occurrence count alone:

| Severity | Score | Criteria |
|----------|-------|----------|
| High | 3 | Credentials (API keys, private keys, passwords), large volumes of financial/PII data, or multiple categories in one object |
| Medium | 2 | Financial data (credit cards, bank accounts), moderate PII exposure |
| Low | 1 | Small amounts of non-credential PII (names, addresses), single-category findings |

**Key rules:**

- Credentials are **always** High regardless of occurrence count
- Severity increases when multiple sensitive data categories appear in the same S3 object
- Custom data identifiers inherit the severity configured at creation time
- Policy findings (bucket-level) use a separate severity scale based on bucket exposure
- Automated discovery findings aggregate across objects — severity reflects bucket-level risk

Refer to [Macie severity scoring documentation](https://docs.aws.amazon.com/macie/latest/user/findings-severity.html) for complete per-finding-type breakdown.

## Service Notes

No service-specific notes.

## Output Sensitivity

Macie finding details (`GetFindings`) contain:

- S3 bucket names and object keys where sensitive data was detected
- Sensitive data categories and occurrence counts (PII, financial, credentials)
- AWS account IDs and resource ARNs
- Classification job configuration details
- Bucket access permissions and encryption status

Present finding severity/type summary and affected bucket counts first. Offer full finding details on request. Never include actual sensitive data samples in output.
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: 471kUpdated 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: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated 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