mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 16:40:24 +00:00
24f816b6a3
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):
- brain/ LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
dispatch, A51 channels, and the OSINT cluster
- knowledge/ LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
MITRE ATT&CK data
- reference/ defensive threat-reference (C3, shhbruh doc) + AdaYaml parser
License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.
Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.
https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
58 lines
1.8 KiB
Markdown
58 lines
1.8 KiB
Markdown
# API Reference: AWS IAM Permission Boundary Agent
|
|
|
|
## Dependencies
|
|
|
|
| Library | Version | Purpose |
|
|
|---------|---------|---------|
|
|
| boto3 | >=1.28 | AWS SDK for IAM permission boundary management |
|
|
|
|
## CLI Usage
|
|
|
|
```bash
|
|
python scripts/agent.py \
|
|
--profile security-admin \
|
|
--region us-east-1 \
|
|
--audit \
|
|
--output-dir /reports/ \
|
|
--output iam_boundary_report.json
|
|
```
|
|
|
|
## Functions
|
|
|
|
### `get_iam_client(profile, region)`
|
|
Creates boto3 IAM client with optional named profile.
|
|
|
|
### `create_permission_boundary(client, policy_name, allowed_services, allowed_regions) -> dict`
|
|
Creates an IAM policy for use as a permission boundary. Includes a DenyBoundaryChanges statement to prevent boundary removal. Uses `client.create_policy()`.
|
|
|
|
### `attach_boundary_to_role(client, role_name, boundary_arn) -> dict`
|
|
Calls `client.put_role_permissions_boundary()` to attach a boundary to a role.
|
|
|
|
### `audit_roles_without_boundary(client) -> list`
|
|
Paginates `client.list_roles()` and identifies roles missing `PermissionsBoundary`.
|
|
|
|
### `audit_boundary_effectiveness(client, role_name) -> dict`
|
|
Calls `client.get_role()`, `list_attached_role_policies()`, `list_role_policies()` to show effective policy stack.
|
|
|
|
### `generate_report(client) -> dict`
|
|
Orchestrates audit and generates compliance report.
|
|
|
|
## boto3 IAM Methods Used
|
|
|
|
| Method | Purpose |
|
|
|--------|---------|
|
|
| `create_policy(PolicyName, PolicyDocument)` | Create boundary policy |
|
|
| `put_role_permissions_boundary(RoleName, PermissionsBoundary)` | Attach boundary |
|
|
| `list_roles()` | Enumerate all roles |
|
|
| `get_role(RoleName)` | Get role details including boundary |
|
|
|
|
## Output Schema
|
|
|
|
```json
|
|
{
|
|
"roles_without_boundary_count": 12,
|
|
"roles_without_boundary": [{"role_name": "dev-role", "arn": "arn:aws:iam::..."}],
|
|
"recommendations": ["Attach permission boundaries to 12 roles"]
|
|
}
|
|
```
|