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.
Works with
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:
Fetches 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:
Restart Cursor to activate analyzing-kubernetes-audit-logs. Access via /analyzing-kubernetes-audit-logs in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
0
total installs
0
this week
8.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
8.6K
stars
| 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')}")
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
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.
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
shadcn/improve
sickn33/antigravity-awesome-skills
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