Claude 24f816b6a3
Consolidate 22 sibling repos into layered organism structure
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
2026-06-10 06:53:01 +00:00

58 lines
2.2 KiB
Markdown

# API Reference: Implementing CloudTrail Log Analysis
## Libraries
### boto3 -- AWS CloudTrail
- **Install**: `pip install boto3`
- **Docs**: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/cloudtrail.html
### Key Methods
| Method | Description |
|--------|-------------|
| `lookup_events()` | Search recent CloudTrail events with filters |
| `describe_trails()` | List configured trails |
| `get_trail_status()` | Check if trail is actively logging |
| `create_trail()` | Create a new CloudTrail trail |
| `start_logging()` / `stop_logging()` | Control trail recording |
| `get_event_selectors()` | View event type configuration |
| `put_event_selectors()` | Configure management/data event capture |
## Lookup Attributes
| AttributeKey | Description |
|-------------|-------------|
| `EventName` | API action name (e.g., `RunInstances`) |
| `Username` | IAM user or role name |
| `ResourceType` | AWS resource type |
| `ResourceName` | Specific resource identifier |
| `EventSource` | AWS service (e.g., `ec2.amazonaws.com`) |
| `ReadOnly` | Filter read vs write events |
## Suspicious Event Names
| Event | Threat Category |
|-------|----------------|
| `StopLogging` / `DeleteTrail` | Anti-forensics |
| `CreateUser` / `CreateAccessKey` | Persistence |
| `AttachUserPolicy` / `PutUserPolicy` | Privilege escalation |
| `ConsoleLogin` (failed) | Brute force |
| `RunInstances` | Resource abuse / cryptomining |
| `AuthorizeSecurityGroupIngress` | Lateral movement |
| `DisableKey` | Ransomware indicator |
## Athena Query Integration
- Create Athena table from CloudTrail S3 logs
- SQL queries for historical analysis beyond 90-day API limit
- Partition by region, year, month for performance
## CloudWatch Logs Insights
- `filter eventName = "ConsoleLogin"` -- Login analysis
- `stats count(*) by eventName` -- API call frequency
- `filter errorCode = "AccessDenied"` -- Permission issues
## External References
- CloudTrail User Guide: https://docs.aws.amazon.com/awscloudtrail/latest/userguide/
- CloudTrail Log Events: https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference.html
- Athena + CloudTrail: https://docs.aws.amazon.com/athena/latest/ug/cloudtrail-logs.html