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/organization-policies.md

View on GitHub
# Organization Policies

## Overview

AWS Organizations supports service-specific policy types for centralized configuration enforcement across member accounts. Multiple security services use this mechanism, each with its own policy type. Organization policies allow administrators to define and enforce service configurations from the management account or delegated administrator, ensuring consistent security posture across the organization.

## Available Policy Types

| Policy Type | Service | Documentation |
|---|---|---|
| `SECURITYHUB_POLICY` | Security Hub | https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_security_hub.html |
| `INSPECTOR_POLICY` | Inspector | https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_policies_inspector.html |

## Common Discovery Pattern

The same CLI pattern applies to all policy types — substitute the appropriate `POLICY_TYPE` value:

```bash
# List policies of a given type
aws organizations list-policies --filter <POLICY_TYPE>

# Get policy document details
aws organizations describe-policy --policy-id <id>

# Check which roots, OUs, or accounts a policy targets
aws organizations list-targets-for-policy --policy-id <id>
```

These are `organizations` namespace APIs — not service-specific APIs like `securityhub` or `inspector2`.

> **Execution environment:** The AWS MCP server is recommended for running these API calls but is not required — standard AWS CLI access is sufficient.

## Read-Only APIs

| API | Purpose |
|-----|---------|
| `organizations:ListPolicies` | List policies by type |
| `organizations:DescribePolicy` | Get policy document and metadata |
| `organizations:ListTargetsForPolicy` | List OUs/accounts a policy applies to |
| `organizations:ListPoliciesForTarget` | List policies applied to a specific OU/account |

## Operator Prerequisites

Organization policy APIs are `organizations` namespace APIs. Access requires one of:

- A role in the Organizations **management account** with `organizations:List*` and `organizations:Describe*` permissions, OR
- A role in a **delegated administrator** account where the management account has configured the delegation policy to grant Organization policy API access to the service's delegated administrator. The standard service onboarding flow configures this delegation.

If `list-policies` returns `AccessDeniedException`, the current role lacks Organizations access. This typically means either:

- The account is not the management account or delegated administrator
- The delegation policy has not been configured to grant these permissions

Report policy status as `Not checked - Organizations access unavailable` and continue with service-specific checks that do not require Organizations permissions.

## Output Sensitivity

Policy documents may reveal organizational structure (OU hierarchy, account assignments), security configuration enforcement rules, and service-specific settings applied across the organization. Present policy summary first; offer full policy document JSON 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