Parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM detection rules.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add mukul975/Anthropic-Cybersecurity-Skills/analyzing-kubernetes-audit-logsCompatible with
Supported agents
| name | analyzing-kubernetes-audit-logs |
| description | 'Parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM detection rules. ' |
| domain | cybersecurity |
| subdomain | container-security |
| tags | - analyzing - kubernetes - audit - logs |
| version | '1.0' |
| author | mahipal |
| license | Apache-2.0 |
| nist_csf | - PR.PS-01 - PR.IR-01 - ID.AM-08 - DE.CM-01 |
Parse Kubernetes audit log files (JSON lines format) to detect security-relevant events including unauthorized access, privilege escalation, and data exfiltration.
import json
with open("/var/log/kubernetes/audit.log") as f:
for line in f:
event = json.loads(line)
verb = event.get("verb")
resource = event.get("objectRef", {}).get("resource")
user = event.get("user", {}).get("username")
if verb == "create" and resource == "pods/exec":
print(f"Pod exec by {user}")
Key events to detect:
# Detect secret enumeration
if verb in ("get", "list") and resource == "secrets":
print(f"Secret access: {user} -> {event['objectRef'].get('name')}")
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionanalyzing-kubernetes-audit-logsExecute the skills CLI command in your project's root directory to begin installation:
epx add mukul975/Anthropic-Cybersecurity-Skills/analyzing-kubernetes-audit-logsFetches analyzing-kubernetes-audit-logs from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/analyzing-kubernetes-audit-logs
Restart Cursor to activate analyzing-kubernetes-audit-logs. Access via /analyzing-kubernetes-audit-logsin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
performing-cryptographic-audit-of-application
mukul975/Anthropic-Cybersecurity-Skills · performing-cryptographic-audit-of-application · same repo
analyzing-network-traffic-with-wireshark
mukul975/Anthropic-Cybersecurity-Skills · analyzing-network-traffic-with-wireshark · same repo
scanning-container-images-with-grype
mukul975/Anthropic-Cybersecurity-Skills · scanning-container-images-with-grype · same repo
executing-red-team-engagement-planning
mukul975/Anthropic-Cybersecurity-Skills · executing-red-team-engagement-planning · same repo
testing-for-broken-access-control
mukul975/Anthropic-Cybersecurity-Skills · testing-for-broken-access-control · same repo
analyzing-outlook-pst-for-email-forensics
mukul975/Anthropic-Cybersecurity-Skills · analyzing-outlook-pst-for-email-forensics · same repo
Solid pick for teams standardizing on skills: analyzing-kubernetes-audit-logs is focused, and the summary matches what you get after install.
Useful defaults in analyzing-kubernetes-audit-logs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added analyzing-kubernetes-audit-logs from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend analyzing-kubernetes-audit-logs for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
analyzing-kubernetes-audit-logs has been reliable in day-to-day use. Documentation quality is above average for community skills.
analyzing-kubernetes-audit-logs fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in analyzing-kubernetes-audit-logs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in analyzing-kubernetes-audit-logs — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
analyzing-kubernetes-audit-logs is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
analyzing-kubernetes-audit-logs has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 74