mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-07-23 21:21:00 +03:00
mukul975
cb8d79e068
- Add validated mitre_attack frontmatter to all 754 skills (286 distinct techniques), verified against MITRE ATT&CK v19.1 via the official mitreattack-python library: 0 revoked, deprecated, or invalid IDs - Curate precise per-skill technique IDs for forensics, malware-analysis, threat-intel, and red-team skills (e.g. DCSync -> T1003.006, Kerberoasting -> T1558.003, Pass-the-Ticket -> T1550.003) - Reconcile v19.1 tactic restructuring: Defense Evasion split into Stealth (TA0005) and Defense Impairment (TA0112); revoked T1562.* family and T1070.001/.002 remapped to active equivalents (T1685.*) - Normalize word-split tags across 35 skills (remove filename-derived stopword tags, add semantic cybersecurity tags) - Add api-reference.md for 3 skills that were missing it - Update README ATT&CK section with accurate v19.1 tactic distribution
88 lines
2.5 KiB
Markdown
88 lines
2.5 KiB
Markdown
---
|
|
name: performing-cloud-native-forensics-with-falco
|
|
description: 'Uses Falco YAML rules for runtime threat detection in containers and
|
|
Kubernetes, monitoring syscalls for shell spawns, file tampering, network anomalies,
|
|
and privilege escalation. Manages Falco rules via the Falco gRPC API and parses
|
|
Falco alert output. Use when building container runtime security or investigating
|
|
k8s cluster compromises.
|
|
|
|
'
|
|
domain: cybersecurity
|
|
subdomain: cloud-security
|
|
tags:
|
|
- cloud-security
|
|
- falco
|
|
- runtime-threat-detection
|
|
- container-forensics
|
|
- kubernetes-security
|
|
- syscall-monitoring
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- PR.IR-01
|
|
- ID.AM-08
|
|
- GV.SC-06
|
|
- DE.CM-01
|
|
mitre_attack:
|
|
- T1078.004
|
|
- T1530
|
|
- T1537
|
|
- T1580
|
|
- T1068
|
|
---
|
|
|
|
# Performing Cloud Native Forensics with Falco
|
|
|
|
|
|
## When to Use
|
|
|
|
- When conducting security assessments that involve performing cloud native forensics with falco
|
|
- When following incident response procedures for related security events
|
|
- When performing scheduled security testing or auditing activities
|
|
- When validating security controls through hands-on testing
|
|
|
|
## Prerequisites
|
|
|
|
- Familiarity with cloud security concepts and tools
|
|
- Access to a test or lab environment for safe execution
|
|
- Python 3.8+ with required dependencies installed
|
|
- Appropriate authorization for any testing activities
|
|
|
|
## Instructions
|
|
|
|
Deploy and manage Falco rules for runtime security detection in containerized
|
|
environments. Parse Falco alerts for incident response.
|
|
|
|
```yaml
|
|
# Custom Falco rule for detecting shell in container
|
|
- rule: Shell Spawned in Container
|
|
desc: Detect shell process started in a container
|
|
condition: >
|
|
spawned_process and container
|
|
and proc.name in (bash, sh, zsh, dash, csh)
|
|
and not proc.pname in (docker-entrypo, supervisord)
|
|
output: >
|
|
Shell spawned in container
|
|
(user=%user.name command=%proc.cmdline container=%container.name
|
|
image=%container.image.repository)
|
|
priority: WARNING
|
|
tags: [container, shell, mitre_execution]
|
|
```
|
|
|
|
Key detection rules:
|
|
1. Shell spawn in non-interactive containers
|
|
2. Sensitive file access (/etc/shadow, /etc/passwd)
|
|
3. Outbound connections from unexpected containers
|
|
4. Privilege escalation via setuid/setgid
|
|
5. Container escape via mount or ptrace
|
|
|
|
## Examples
|
|
|
|
```bash
|
|
# Run Falco with custom rules
|
|
falco -r /etc/falco/custom_rules.yaml -o json_output=true
|
|
# Parse JSON alerts
|
|
cat /var/log/falco/alerts.json | python3 -c "import json,sys; [print(json.loads(l)['output']) for l in sys.stdin]"
|
|
```
|