Skip to content
View reninjk's full-sized avatar

Block or report reninjk

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
reninjk/README.md

Hi, I'm Ben πŸ‘‹

SOC Manager | Detection Engineer | Security Automation Advocate

I run the SOC day-to-day. My focus is detection engineering, incident response, and building automation that removes grunt work from the analyst queue. The goal is always the same: find real threats faster and cut the noise.


πŸ”’ What I Do

  • Security Operations Leadership: Managing SOC teams, shift coverage, SLA governance, and analyst development
  • Detection Engineering: Writing and tuning detection rules (Sigma, KQL, SPL) mapped to MITRE ATT&CK
  • Incident Response: Running IR playbooks from phishing to ransomware; P1 incident commander
  • Security Automation: Building Python tools for alert triage, IOC enrichment, and SOAR integration
  • Threat Intelligence: Actor profiling, TI feed management, IOC lifecycle, MISP integration
  • Compliance & Reporting: NIST CSF, ISO 27001; board-level executive summaries and CISO dashboards

πŸ“Š GitHub Stats

GitHub Stats Top Languages

GitHub Streak


🚧 Currently Building

Project Status Description
SOAR Webhook Listener βœ… Complete FastAPI receiver with auto-triage and IOC enrichment
ATT&CK Coverage Expansion πŸ”„ In Progress Growing Sigma rule library across all tactics
DNS Beaconing Detection βœ… Complete High-fidelity C2 detection via DNS frequency analysis
Threat Actor Profiles πŸ”„ In Progress Structured actor profiles with full TTP mapping
Quarterly Compliance Reporting ⏳ Planned Automated NIST CSF gap analysis + board pack

πŸ›  SOC Repositories

Repository Description CI
🚨 soc-incident-response IR playbooks, runbooks, and incident report templates covering phishing through ransomware CI
πŸ” soc-detection-rules Sigma detection rules and threat hunting queries mapped to MITRE ATT&CK CI
βš™οΈ soc-automation Python tools for alert triage, IOC enrichment, SOAR webhook integration, and metrics CI
πŸ“Š soc-compliance-reporting NIST CSF audit checklists, SOC KPI metrics, weekly/monthly executive report templates CI
🌐 soc-threat-intelligence IOC feeds, threat actor profiles with TTP mapping, TI reports, and MISP integration CI
πŸ›‘οΈ soc-vulnerability-management Vulnerability workflows, patch SLA tracking, CVSS risk scoring, and remediation processes CI
πŸŽ“ soc-training-lab Analyst onboarding, training scenarios, tabletop exercises (ransomware + BEC), cert roadmap CI

🧰 Tech & Tools

SIEM / Detection Β  Splunk Microsoft Sentinel Elastic

Languages & Scripting Β  Python Bash YAML

Detection Formats Β  Sigma KQL SPL

Frameworks & Standards Β  MITRE ATT&CK NIST CSF ISO 27001

DevOps & Automation Β  GitHub Actions FastAPI Docker


🎯 MITRE ATT&CK Coverage

Current Sigma rule coverage across tactics (soc-detection-rules):

Tactic Rules Key Techniques
Initial Access 1 T1566 Phishing
Execution 1 T1059 Scripting
Persistence 1 T1053 Scheduled Task
Privilege Escalation 1 T1053.005 Scheduled Task
Defence Evasion 1 T1562 Disable Tools
Credential Access 2 T1003.001 LSASS, T1110 Brute Force
Discovery 1 T1082 System Info
Lateral Movement 2 T1021.001 RDP, T1021.002 SMB
Command & Control 1 T1071.004 DNS Beaconing
Impact 1 T1486 Ransomware
TOTAL 12 Expanding monthly

🧠 My SOC Philosophy

"A SOC that can't measure itself, can't improve itself."

I believe in three pillars for effective security operations:

  1. Detect more, alert less: High-fidelity detections beat alert fatigue every time. Tune ruthlessly.
  2. Automate the repeatable: Every manual task a machine can do is analyst time freed for real hunting.
  3. Communicate clearly: A P1 incident handled perfectly but reported poorly loses stakeholder trust.

πŸ“ Repository Structure Philosophy

All my SOC repos follow the same principles:

  • βœ… Version-controlled: every playbook, rule, and script change tracked in Git
  • βœ… CI/CD validated: GitHub Actions check structure, syntax, and links on every push
  • βœ… Framework-mapped: detection rules and playbooks tagged to MITRE ATT&CK tactics
  • βœ… Tool-agnostic where possible: Sigma rules convert to Splunk SPL, Microsoft KQL, Elastic EQL
  • βœ… Peer-reviewed: all production changes go through PR review
  • βœ… OPSEC-first: no real credentials, IOCs, or employer data in any repo

πŸ“¬ Get in Touch

  • GitHub: @reninjk
  • Open to connecting with fellow SOC practitioners, detection engineers, and IR professionals

"Security is not a product, but a process." - Bruce Schneier

Pinned Loading

  1. soc-automation soc-automation Public

    SOC security automation scripts for alert triage, IOC enrichment, and incident response workflows

    Python

  2. soc-detection-rules soc-detection-rules Public

    SIEM detection rules, Sigma rules, threat hunting queries, and MITRE ATT&CK mappings

  3. soc-incident-response soc-incident-response Public

    SOC Incident Response playbooks, runbooks, IR templates, and escalation procedures

  4. soc-threat-intelligence soc-threat-intelligence Public

    SOC threat intelligence: IOC feeds, actor profiles, TI reports, and MISP integration guides

    Python

  5. soc-training-lab soc-training-lab Public

    SOC analyst onboarding, training scenarios, tabletop exercises, tool quick-reference cards, and certification roadmap

    1

  6. soc-compliance-reporting soc-compliance-reporting Public

    SOC compliance frameworks, audit checklists, metrics dashboards, and automated reporting templates