[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M739NHMNAF116BY0C563AS4A":3,"skill-same:01M739NHMNAF116BY0C563AS4A":106},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M739NHMNAF116BY0C563AS4A","building-soc-escalation-matrix",null,"Build a structured SOC escalation matrix defining severity tiers, response SLAs, escalation paths, and notification procedures for security incidents.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fbuilding-soc-escalation-matrix\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fbuilding-soc-escalation-matrix\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: building-soc-escalation-matrix\ndescription: Build a structured SOC escalation matrix defining severity tiers, response\n  SLAs, escalation paths, and notification procedures for security incidents.\ndomain: cybersecurity\nsubdomain: soc-operations\ntags:\n- soc\n- escalation\n- incident-management\n- severity\n- sla\n- triage\n- tiered-soc\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- RS.MA-01\n- DE.AE-06\nmitre_attack:\n- T1078\n- T1071\n- T1041\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\n---\n\n# Building SOC Escalation Matrix\n\n## Overview\n\nA SOC escalation matrix defines how security incidents move through the organization based on severity, impact, and response requirements. Modern SOCs use context-driven escalation combining business risk, asset criticality, and data sensitivity rather than purely severity-based models. Organizations using AI and automation in their SOC cut detection-and-containment lifecycle to approximately 161 days, an 80-day improvement over the 241-day industry average.\n\n\n## When to Use\n\n- When deploying or configuring building soc escalation matrix capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with soc operations concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## SOC Tier Structure\n\n### Tier 1 - Alert Triage Analyst\n- Monitors SIEM dashboards and alert queues\n- Performs initial alert classification (true\u002Ffalse positive)\n- Handles P3 and P4 incidents to resolution\n- Escalates P1 and P2 incidents to Tier 2 within SLA\n- Documents initial findings in ticketing system\n\n### Tier 2 - Incident Analyst\n- Performs deep-dive investigation on escalated incidents\n- Conducts root cause analysis and scoping\n- Executes containment procedures\n- Handles P2 incidents to resolution\n- Escalates P1 incidents to Tier 3 or management\n\n### Tier 3 - Senior Analyst \u002F Threat Hunter\n- Handles P1 critical incidents and APT investigations\n- Performs proactive threat hunting\n- Develops detection rules and playbooks\n- Conducts malware reverse engineering\n- Leads incident response for major breaches\n\n### Management Escalation\n- SOC Manager: Operational decisions, resource allocation\n- CISO: Business impact decisions, executive communication\n- Legal\u002FPR: Data breach notification, media response\n- External IR: Third-party incident response engagement\n\n## Severity Classification\n\n### P1 - Critical\n\n| Attribute | Value |\n|---|---|\n| Impact | Active data breach, ransomware spreading, critical systems compromised |\n| Business Impact | Revenue loss, regulatory exposure, customer data at risk |\n| Initial Response | 15 minutes |\n| Escalation to Tier 2 | Immediate |\n| Escalation to Management | 30 minutes |\n| Resolution Target | 4 hours |\n| Communication | Every 30 minutes to stakeholders |\n| Examples | Active ransomware, confirmed data exfiltration, domain admin compromise |\n\n### P2 - High\n\n| Attribute | Value |\n|---|---|\n| Impact | Confirmed compromise, limited scope, no active exfiltration |\n| Business Impact | Potential revenue impact, contained risk |\n| Initial Response | 30 minutes |\n| Escalation to Tier 2 | 30 minutes if unresolved |\n| Escalation to Management | 2 hours |\n| Resolution Target | 8 hours |\n| Communication | Every 2 hours to SOC management |\n| Examples | Compromised user account, malware on single endpoint, insider threat indicator |\n\n### P3 - Medium\n\n| Attribute | Value |\n|---|---|\n| Impact | Suspicious activity requiring investigation |\n| Business Impact | Low immediate risk |\n| Initial Response | 4 hours |\n| Escalation to Tier 2 | 8 hours if unresolved |\n| Resolution Target | 24 hours |\n| Communication | Daily status update |\n| Examples | Policy violation, failed brute force, suspicious email report |\n\n### P4 - Low\n\n| Attribute | Value |\n|---|---|\n| Impact | Informational alerts, routine security events |\n| Business Impact | Minimal |\n| Initial Response | 8 hours |\n| Escalation | Only if pattern emerges |\n| Resolution Target | 72 hours |\n| Communication | Weekly summary |\n| Examples | Vulnerability scan findings, expired certificates, policy exceptions |\n\n## Escalation Decision Matrix\n\n```\n                    Asset Criticality\n                    Low        Medium      High        Critical\nSeverity  Low      P4         P4          P3          P3\n          Medium   P4         P3          P2          P2\n          High     P3         P2          P2          P1\n          Critical P2         P1          P1          P1\n```\n\n## Context-Driven Escalation Triggers\n\n### Automatic Escalation (no analyst decision needed)\n\n| Trigger | Action |\n|---|---|\n| Ransomware detected on any endpoint | P1 - Immediate Tier 3 + Management |\n| Domain admin account compromise | P1 - Immediate Tier 3 + Management |\n| Active data exfiltration to external IP | P1 - Immediate Tier 3 + Management |\n| Critical infrastructure (DC, SCADA) alert | P1 - Immediate Tier 2 minimum |\n| Executive account anomaly | P2 - Immediate Tier 2 |\n| Multiple hosts with same malware | P1 - Immediate Tier 2 |\n\n### Time-Based Escalation\n\n| Condition | Action |\n|---|---|\n| P2 unresolved after 4 hours | Escalate to Tier 3 |\n| P3 unresolved after 12 hours | Escalate to Tier 2 |\n| Any incident unresolved past SLA | Escalate to SOC Manager |\n| P1 unresolved after 2 hours | Escalate to CISO |\n\n## Communication Templates\n\n### P1 Initial Notification\n\n```\nSUBJECT: [P1 CRITICAL] Security Incident - {Incident_ID}\n\nIncident Summary:\n- Type: {incident_type}\n- Affected Systems: {systems}\n- Affected Users: {users}\n- Current Status: {status}\n- Assigned To: {analyst}\n\nImpact Assessment:\n- Business Impact: {impact}\n- Data at Risk: {data_risk}\n- Containment Status: {containment}\n\nNext Actions:\n- {action_1}\n- {action_2}\n\nNext Update: {time} (30-minute intervals)\nBridge Line: {conference_details}\n```\n\n## Escalation Matrix Implementation\n\n### SOAR Integration\n\n```yaml\n# XSOAR escalation playbook trigger\ntrigger:\n  condition: incident.severity == \"critical\" AND incident.asset_criticality == \"high\"\n  action:\n    - assign_tier: 3\n    - notify: [soc_manager, ciso]\n    - create_war_room: true\n    - start_bridge: true\n    - set_sla: 4h\n\nauto_escalation_rules:\n  - name: P2 Time-Based Escalation\n    condition: incident.severity == \"high\" AND incident.age > 4h AND incident.status != \"resolved\"\n    action:\n      - escalate_tier: 3\n      - notify: soc_manager\n      - add_comment: \"Auto-escalated due to SLA breach\"\n```\n\n## References\n\n- [Torq - Threat Escalation Matrix for Modern Security Challenges](https:\u002F\u002Ftorq.io\u002Fblog\u002Fescalation-matrix\u002F)\n- [ClearFeed - Incident Escalation Matrix](https:\u002F\u002Fclearfeed.ai\u002Fblogs\u002Fincident-escalation-matrix)\n- [Vectra - SOC Operations Guide](https:\u002F\u002Fwww.vectra.ai\u002Ftopics\u002Fsoc-operations)\n- [Runframe - Incident Priority Levels Explained](https:\u002F\u002Frunframe.io\u002Flearn\u002Fincident-priority)\n","# Building SOC Escalation Matrix\n\n## Overview\n\nA SOC escalation matrix defines how security incidents move through the organization based on severity, impact, and response requirements. Modern SOCs use context-driven escalation combining business risk, asset criticality, and data sensitivity rather than purely severity-based models. Organizations using AI and automation in their SOC cut detection-and-containment lifecycle to approximately 161 days, an 80-day improvement over the 241-day industry average.\n\n\n## When to Use\n\n- When deploying or configuring building soc escalation matrix capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with soc operations concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## SOC Tier Structure\n\n### Tier 1 - Alert Triage Analyst\n- Monitors SIEM dashboards and alert queues\n- Performs initial alert classification (true\u002Ffalse positive)\n- Handles P3 and P4 incidents to resolution\n- Escalates P1 and P2 incidents to Tier 2 within SLA\n- Documents initial findings in ticketing system\n\n### Tier 2 - Incident Analyst\n- Performs deep-dive investigation on escalated incidents\n- Conducts root cause analysis and scoping\n- Executes containment procedures\n- Handles P2 incidents to resolution\n- Escalates P1 incidents to Tier 3 or management\n\n### Tier 3 - Senior Analyst \u002F Threat Hunter\n- Handles P1 critical incidents and APT investigations\n- Performs proactive threat hunting\n- Develops detection rules and playbooks\n- Conducts malware reverse engineering\n- Leads incident response for major breaches\n\n### Management Escalation\n- SOC Manager: Operational decisions, resource allocation\n- CISO: Business impact decisions, executive communication\n- Legal\u002FPR: Data breach notification, media response\n- External IR: Third-party incident response engagement\n\n## Severity Classification\n\n### P1 - Critical\n\n| Attribute | Value |\n|---|---|\n| Impact | Active data breach, ransomware spreading, critical systems compromised |\n| Business Impact | Revenue loss, regulatory exposure, customer data at risk |\n| Initial Response | 15 minutes |\n| Escalation to Tier 2 | Immediate |\n| Escalation to Management | 30 minutes |\n| Resolution Target | 4 hours |\n| Communication | Every 30 minutes to stakeholders |\n| Examples | Active ransomware, confirmed data exfiltration, domain admin compromise |\n\n### P2 - High\n\n| Attribute | Value |\n|---|---|\n| Impact | Confirmed compromise, limited scope, no active exfiltration |\n| Business Impact | Potential revenue impact, contained risk |\n| Initial Response | 30 minutes |\n| Escalation to Tier 2 | 30 minutes if unresolved |\n| Escalation to Management | 2 hours |\n| Resolution Target | 8 hours |\n| Communication | Every 2 hours to SOC management |\n| Examples | Compromised user account, malware on single endpoint, insider threat indicator |\n\n### P3 - Medium\n\n| Attribute | Value |\n|---|---|\n| Impact | Suspicious activity requiring investigation |\n| Business Impact | Low immediate risk |\n| Initial Response | 4 hours |\n| Escalation to Tier 2 | 8 hours if unresolved |\n| Resolution Target | 24 hours |\n| Communication | Daily status update |\n| Examples | Policy violation, failed brute force, suspicious email report |\n\n### P4 - Low\n\n| Attribute | Value |\n|---|---|\n| Impact | Informational alerts, routine security events |\n| Business Impact | Minimal |\n| Initial Response | 8 hours |\n| Escalation | Only if pattern emerges |\n| Resolution Target | 72 hours |\n| Communication | Weekly summary |\n| Examples | Vulnerability scan findings, expired certificates, policy exceptions |\n\n## Escalation Decision Matrix\n\n```\n                    Asset Criticality\n                    Low        Medium      High        Critical\nSeverity  Low      P4         P4          P3          P3\n          Medium   P4         P3          P2          P2\n          High     P3         P2          P2          P1\n          Critical P2         P1          P1          P1\n```\n\n## Context-Driven Escalation Triggers\n\n### Automatic Escalation (no analyst decision needed)\n\n| Trigger | Action |\n|---|---|\n| Ransomware detected on any endpoint | P1 - Immediate Tier 3 + Management |\n| Domain admin account compromise | P1 - Immediate Tier 3 + Management |\n| Active data exfiltration to external IP | P1 - Immediate Tier 3 + Management |\n| Critical infrastructure (DC, SCADA) alert | P1 - Immediate Tier 2 minimum |\n| Executive account anomaly | P2 - Immediate Tier 2 |\n| Multiple hosts with same malware | P1 - Immediate Tier 2 |\n\n### Time-Based Escalation\n\n| Condition | Action |\n|---|---|\n| P2 unresolved after 4 hours | Escalate to Tier 3 |\n| P3 unresolved after 12 hours | Escalate to Tier 2 |\n| Any incident unresolved past SLA | Escalate to SOC Manager |\n| P1 unresolved after 2 hours | Escalate to CISO |\n\n## Communication Templates\n\n### P1 Initial Notification\n\n```\nSUBJECT: [P1 CRITICAL] Security Incident - {Incident_ID}\n\nIncident Summary:\n- Type: {incident_type}\n- Affected Systems: {systems}\n- Affected Users: {users}\n- Current Status: {status}\n- Assigned To: {analyst}\n\nImpact Assessment:\n- Business Impact: {impact}\n- Data at Risk: {data_risk}\n- Containment Status: {containment}\n\nNext Actions:\n- {action_1}\n- {action_2}\n\nNext Update: {time} (30-minute intervals)\nBridge Line: {conference_details}\n```\n\n## Escalation Matrix Implementation\n\n### SOAR Integration\n\n```yaml\n# XSOAR escalation playbook trigger\ntrigger:\n  condition: incident.severity == \"critical\" AND incident.asset_criticality == \"high\"\n  action:\n    - assign_tier: 3\n    - notify: [soc_manager, ciso]\n    - create_war_room: true\n    - start_bridge: true\n    - set_sla: 4h\n\nauto_escalation_rules:\n  - name: P2 Time-Based Escalation\n    condition: incident.severity == \"high\" AND incident.age > 4h AND incident.status != \"resolved\"\n    action:\n      - escalate_tier: 3\n      - notify: soc_manager\n      - add_comment: \"Auto-escalated due to SLA breach\"\n```\n\n## References\n\n- [Torq - Threat Escalation Matrix for Modern Security Challenges](https:\u002F\u002Ftorq.io\u002Fblog\u002Fescalation-matrix\u002F)\n- [ClearFeed - Incident Escalation Matrix](https:\u002F\u002Fclearfeed.ai\u002Fblogs\u002Fincident-escalation-matrix)\n- [Vectra - SOC Operations Guide](https:\u002F\u002Fwww.vectra.ai\u002Ftopics\u002Fsoc-operations)\n- [Runframe - Incident Priority Levels Explained](https:\u002F\u002Frunframe.io\u002Flearn\u002Fincident-priority)\n",{"name":5,"tags":25,"author":33,"domain":34,"source":35,"license":15,"version":36,"nist_csf":37,"subdomain":42,"description":7,"mitre_attack":43,"source_commit":47},[26,27,28,29,30,31,32],"soc","escalation","incident-management","severity","sla","triage","tiered-soc","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[38,39,40,41],"DE.CM-01","DE.AE-02","RS.MA-01","DE.AE-06","soc-operations",[44,45,46],"T1078","T1071","T1041","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fbuilding-soc-escalation-matrix",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill building-soc-escalation-matrix",{"tool":64,"command":65},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill building-soc-escalation-matrix",{"tool":67,"command":68},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill building-soc-escalation-matrix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fbuilding-soc-escalation-matrix\u002FSKILL.md",true,[72,78,82,88,92,96,102],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"assets\u002Ftemplate.md","ASSET","资产文件",965,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fbuilding-soc-escalation-matrix\u002Fassets\u002Ftemplate.md",{"path":79,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fapi-reference.md","REFERENCE","参考文档",1872,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fbuilding-soc-escalation-matrix\u002Freferences\u002Fapi-reference.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fstandards.md",1098,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fbuilding-soc-escalation-matrix\u002Freferences\u002Fstandards.md",{"path":93,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fworkflows.md",901,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fbuilding-soc-escalation-matrix\u002Freferences\u002Fworkflows.md",{"path":97,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fagent.py","SCRIPT","脚本",7570,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fbuilding-soc-escalation-matrix\u002Fscripts\u002Fagent.py",{"path":103,"resourceType":98,"resourceTypeDesc":99,"sizeBytes":104,"sourceHtmlUrl":105},"scripts\u002Fprocess.py",8239,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fbuilding-soc-escalation-matrix\u002Fscripts\u002Fprocess.py",[107,115,122,130,138,146],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":111,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]