[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73B8BV9S5XMB1CMPA85F28Y":3,"skill-same:01M73B8BV9S5XMB1CMPA85F28Y":92},{"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":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M73B8BV9S5XMB1CMPA85F28Y","evaluating-threat-intelligence-platforms",null,"Evaluates and selects Threat Intelligence Platform (TIP) products based on organizational requirements including feed integration capability, STIX\u002FTAXII support, workflow automation, analyst interface, and total cost of ownership. Use when conducting a TIP procurement, migrating between TIP solutions, or assessing whether the current TIP meets program maturity requirements. Activates for requests involving ThreatConnect, MISP, OpenCTI, Anomali, EclecticIQ, or TIP procurement decisions.","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\u002Fevaluating-threat-intelligence-platforms\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fevaluating-threat-intelligence-platforms\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: evaluating-threat-intelligence-platforms\ndescription: 'Evaluates and selects Threat Intelligence Platform (TIP) products based\n  on organizational requirements including feed integration capability, STIX\u002FTAXII\n  support, workflow automation, analyst interface, and total cost of ownership. Use\n  when conducting a TIP procurement, migrating between TIP solutions, or assessing\n  whether the current TIP meets program maturity requirements. Activates for requests\n  involving ThreatConnect, MISP, OpenCTI, Anomali, EclecticIQ, or TIP procurement\n  decisions.\n\n  '\ndomain: cybersecurity\nsubdomain: threat-intelligence\ntags:\n- TIP\n- ThreatConnect\n- MISP\n- OpenCTI\n- Anomali\n- EclecticIQ\n- STIX-TAXII\n- CTI-program\n- procurement\nversion: 1.0.0\nauthor: team-cybersecurity\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- ID.RA-05\n- DE.CM-01\n- DE.AE-02\nmitre_attack:\n- T1591\n- T1592\n- T1593\n- T1589\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\n---\n# Evaluating Threat Intelligence Platforms\n\n## When to Use\n\nUse this skill when:\n- Conducting a formal RFP or vendor evaluation for a TIP solution\n- Assessing whether the current TIP (e.g., MISP) needs to be replaced or augmented as the CTI program scales\n- Establishing evaluation criteria aligned to organizational maturity and budget\n\n**Do not use** this skill for evaluating feed quality independently of the TIP — feed evaluation is a separate workflow focused on data quality rather than platform capabilities.\n\n## Prerequisites\n\n- Documented CTI program requirements: team size, feed sources, integration targets, use cases\n- Budget range and procurement timeline\n- Technical staff who will administer the platform (Python\u002FAPI experience for open-source TIPs)\n- List of current and planned integrations (SIEM, SOAR, EDR, firewalls)\n\n## Workflow\n\n### Step 1: Define Evaluation Criteria\n\nStructure requirements into mandatory (M) and desired (D) categories:\n\n**Core TIP Functions**:\n- M: STIX 2.1 import\u002Fexport with TAXII 2.1 server\n- M: REST API for automated IOC ingestion and export\n- M: Indicator deduplication and TTL management\n- M: TLP classification enforcement\n- D: Built-in MITRE ATT&CK integration and technique tagging\n- D: Graph visualization of indicator relationships\n- D: Workflow automation for analyst triage\n\n**Integrations**:\n- M: SIEM integration (Splunk, Sentinel, QRadar) via syslog, API, or native connector\n- M: EDR integration for IOC push (CrowdStrike, Defender, SentinelOne)\n- D: SOAR integration (XSOAR, Splunk SOAR) for playbook triggers\n- D: Ticketing system (ServiceNow, Jira) for intelligence task tracking\n\n**Operational**:\n- M: Role-based access control with TLP-aware data segregation\n- M: Audit logging for all analyst actions\n- D: Multi-tenancy for MSSP use cases\n\n### Step 2: Evaluate Major TIP Options\n\n**MISP (Open Source)**:\n- Cost: Free (self-hosted infrastructure cost only)\n- Strengths: Largest community, 250+ modules, extensive ISAC usage, STIX 2.0 native\n- Weaknesses: Requires dedicated admin, limited visualization, UI dated\n- Best for: Budget-constrained teams with technical staff; government\u002FISAC sharing programs\n\n**OpenCTI (Open Source)**:\n- Cost: Free (self-hosted); paid SaaS at ~$3,000–$15,000\u002Fyear\n- Strengths: Native STIX 2.1, graph visualization, ATT&CK integration, modern API\n- Weaknesses: Resource-intensive deployment (Elasticsearch, MinIO required)\n- Best for: Teams wanting open source with modern UX; SOC\u002FCTI integration focus\n\n**ThreatConnect (Commercial)**:\n- Cost: $50,000–$500,000\u002Fyear depending on scale\n- Strengths: End-to-end CTI lifecycle, playbook automation, TC Exchange marketplace, analyst workflow\n- Weaknesses: High cost; complex implementation; best value at larger scale\n- Best for: Mature enterprise CTI programs; MSSPs; red team\u002Fblue team integration\n\n**Anomali ThreatStream (Commercial)**:\n- Cost: $30,000–$200,000\u002Fyear\n- Strengths: Strong feed aggregation, Splunk-native integration, extensive pre-built connectors\n- Weaknesses: Graph visualization weaker than OpenCTI; UI refresh lagging\n- Best for: Splunk-heavy environments; teams prioritizing feed volume over analysis workflows\n\n**EclecticIQ Platform (Commercial)**:\n- Cost: $40,000–$300,000\u002Fyear\n- Strengths: STIX 2.1 native, collaborative intelligence workbench, strong European customer base\n- Weaknesses: Smaller partner ecosystem than ThreatConnect\n- Best for: Teams with MITRE ATT&CK-centric workflows; EMEA-focused organizations\n\n### Step 3: Conduct Proof of Concept\n\nRequest 30-day PoC from finalists. Test:\n1. Feed onboarding: Can your top 5 feeds be ingested within 4 hours?\n2. SIEM integration: Can enriched IOCs push to your SIEM in \u003C5 minutes?\n3. ATT&CK mapping: Can analysts tag indicators with ATT&CK techniques efficiently?\n4. Report generation: Can the platform produce a tactical IOC bulletin with one click?\n5. API performance: Can the REST API handle 10,000 indicator queries per day?\n\n### Step 4: Score and Select\n\nUse weighted scoring matrix (weight each criterion by organizational priority):\n```\nCriterion                 Weight   Vendor A   Vendor B\nSTIX 2.1 compliance       20%      95         85\nSIEM integration          25%      90         70\nATT&CK mapping            15%      85         95\nCost (inverse)            20%      60         90\nUI\u002Fanalyst experience     10%      80         75\nVendor support quality    10%      85         80\nTOTAL                     100%     82.0       81.5\n```\n\n### Step 5: Implementation and Onboarding Planning\n\nPlan 90-day implementation:\n- Week 1–2: Infrastructure deployment (cloud or on-prem)\n- Week 3–4: Feed onboarding and deduplication tuning\n- Week 5–6: SIEM\u002FSOAR integration and testing\n- Week 7–8: Analyst workflow configuration and training\n- Week 9–12: Operational validation and go-live\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **TIP** | Threat Intelligence Platform — software for collecting, processing, analyzing, and disseminating cyber threat intelligence |\n| **TAXII Server** | Component of a TIP that serves STIX bundles to consuming systems on request |\n| **TC Exchange** | ThreatConnect's commercial marketplace for pre-built feed integrations and app connectors |\n| **Multi-tenancy** | TIP capability to serve multiple organizational units or customers with isolated data environments |\n| **Deduplication** | Process of identifying and merging duplicate indicators within a TIP to reduce analyst noise |\n\n## Tools & Systems\n\n- **MISP**: Open-source TIP used by 6,000+ organizations; strongest ISAC\u002Fgovernment community integration\n- **OpenCTI**: Modern open-source TIP with native STIX 2.1 and graph-based analysis\n- **ThreatConnect**: Enterprise commercial TIP with lifecycle management and SOAR playbook integration\n- **Anomali ThreatStream**: Commercial TIP with strong Splunk ecosystem integration\n- **EclecticIQ**: Commercial TIP with ATT&CK-centric workflow design\n\n## Common Pitfalls\n\n- **Selecting TIP before defining requirements**: Technology selection before use case definition leads to expensive mismatches.\n- **Underestimating administration burden**: MISP and OpenCTI require dedicated admin time (minimum 0.25 FTE); budget accordingly.\n- **Ignoring data migration costs**: Moving historical intelligence from one TIP to another is costly and often impractical for legacy systems.\n- **Not testing SIEM integration in PoC**: TIP value depends heavily on downstream integration quality; always test SIEM\u002FSOAR connectivity during evaluation.\n","# Evaluating Threat Intelligence Platforms\n\n## When to Use\n\nUse this skill when:\n- Conducting a formal RFP or vendor evaluation for a TIP solution\n- Assessing whether the current TIP (e.g., MISP) needs to be replaced or augmented as the CTI program scales\n- Establishing evaluation criteria aligned to organizational maturity and budget\n\n**Do not use** this skill for evaluating feed quality independently of the TIP — feed evaluation is a separate workflow focused on data quality rather than platform capabilities.\n\n## Prerequisites\n\n- Documented CTI program requirements: team size, feed sources, integration targets, use cases\n- Budget range and procurement timeline\n- Technical staff who will administer the platform (Python\u002FAPI experience for open-source TIPs)\n- List of current and planned integrations (SIEM, SOAR, EDR, firewalls)\n\n## Workflow\n\n### Step 1: Define Evaluation Criteria\n\nStructure requirements into mandatory (M) and desired (D) categories:\n\n**Core TIP Functions**:\n- M: STIX 2.1 import\u002Fexport with TAXII 2.1 server\n- M: REST API for automated IOC ingestion and export\n- M: Indicator deduplication and TTL management\n- M: TLP classification enforcement\n- D: Built-in MITRE ATT&CK integration and technique tagging\n- D: Graph visualization of indicator relationships\n- D: Workflow automation for analyst triage\n\n**Integrations**:\n- M: SIEM integration (Splunk, Sentinel, QRadar) via syslog, API, or native connector\n- M: EDR integration for IOC push (CrowdStrike, Defender, SentinelOne)\n- D: SOAR integration (XSOAR, Splunk SOAR) for playbook triggers\n- D: Ticketing system (ServiceNow, Jira) for intelligence task tracking\n\n**Operational**:\n- M: Role-based access control with TLP-aware data segregation\n- M: Audit logging for all analyst actions\n- D: Multi-tenancy for MSSP use cases\n\n### Step 2: Evaluate Major TIP Options\n\n**MISP (Open Source)**:\n- Cost: Free (self-hosted infrastructure cost only)\n- Strengths: Largest community, 250+ modules, extensive ISAC usage, STIX 2.0 native\n- Weaknesses: Requires dedicated admin, limited visualization, UI dated\n- Best for: Budget-constrained teams with technical staff; government\u002FISAC sharing programs\n\n**OpenCTI (Open Source)**:\n- Cost: Free (self-hosted); paid SaaS at ~$3,000–$15,000\u002Fyear\n- Strengths: Native STIX 2.1, graph visualization, ATT&CK integration, modern API\n- Weaknesses: Resource-intensive deployment (Elasticsearch, MinIO required)\n- Best for: Teams wanting open source with modern UX; SOC\u002FCTI integration focus\n\n**ThreatConnect (Commercial)**:\n- Cost: $50,000–$500,000\u002Fyear depending on scale\n- Strengths: End-to-end CTI lifecycle, playbook automation, TC Exchange marketplace, analyst workflow\n- Weaknesses: High cost; complex implementation; best value at larger scale\n- Best for: Mature enterprise CTI programs; MSSPs; red team\u002Fblue team integration\n\n**Anomali ThreatStream (Commercial)**:\n- Cost: $30,000–$200,000\u002Fyear\n- Strengths: Strong feed aggregation, Splunk-native integration, extensive pre-built connectors\n- Weaknesses: Graph visualization weaker than OpenCTI; UI refresh lagging\n- Best for: Splunk-heavy environments; teams prioritizing feed volume over analysis workflows\n\n**EclecticIQ Platform (Commercial)**:\n- Cost: $40,000–$300,000\u002Fyear\n- Strengths: STIX 2.1 native, collaborative intelligence workbench, strong European customer base\n- Weaknesses: Smaller partner ecosystem than ThreatConnect\n- Best for: Teams with MITRE ATT&CK-centric workflows; EMEA-focused organizations\n\n### Step 3: Conduct Proof of Concept\n\nRequest 30-day PoC from finalists. Test:\n1. Feed onboarding: Can your top 5 feeds be ingested within 4 hours?\n2. SIEM integration: Can enriched IOCs push to your SIEM in \u003C5 minutes?\n3. ATT&CK mapping: Can analysts tag indicators with ATT&CK techniques efficiently?\n4. Report generation: Can the platform produce a tactical IOC bulletin with one click?\n5. API performance: Can the REST API handle 10,000 indicator queries per day?\n\n### Step 4: Score and Select\n\nUse weighted scoring matrix (weight each criterion by organizational priority):\n```\nCriterion                 Weight   Vendor A   Vendor B\nSTIX 2.1 compliance       20%      95         85\nSIEM integration          25%      90         70\nATT&CK mapping            15%      85         95\nCost (inverse)            20%      60         90\nUI\u002Fanalyst experience     10%      80         75\nVendor support quality    10%      85         80\nTOTAL                     100%     82.0       81.5\n```\n\n### Step 5: Implementation and Onboarding Planning\n\nPlan 90-day implementation:\n- Week 1–2: Infrastructure deployment (cloud or on-prem)\n- Week 3–4: Feed onboarding and deduplication tuning\n- Week 5–6: SIEM\u002FSOAR integration and testing\n- Week 7–8: Analyst workflow configuration and training\n- Week 9–12: Operational validation and go-live\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **TIP** | Threat Intelligence Platform — software for collecting, processing, analyzing, and disseminating cyber threat intelligence |\n| **TAXII Server** | Component of a TIP that serves STIX bundles to consuming systems on request |\n| **TC Exchange** | ThreatConnect's commercial marketplace for pre-built feed integrations and app connectors |\n| **Multi-tenancy** | TIP capability to serve multiple organizational units or customers with isolated data environments |\n| **Deduplication** | Process of identifying and merging duplicate indicators within a TIP to reduce analyst noise |\n\n## Tools & Systems\n\n- **MISP**: Open-source TIP used by 6,000+ organizations; strongest ISAC\u002Fgovernment community integration\n- **OpenCTI**: Modern open-source TIP with native STIX 2.1 and graph-based analysis\n- **ThreatConnect**: Enterprise commercial TIP with lifecycle management and SOAR playbook integration\n- **Anomali ThreatStream**: Commercial TIP with strong Splunk ecosystem integration\n- **EclecticIQ**: Commercial TIP with ATT&CK-centric workflow design\n\n## Common Pitfalls\n\n- **Selecting TIP before defining requirements**: Technology selection before use case definition leads to expensive mismatches.\n- **Underestimating administration burden**: MISP and OpenCTI require dedicated admin time (minimum 0.25 FTE); budget accordingly.\n- **Ignoring data migration costs**: Moving historical intelligence from one TIP to another is costly and often impractical for legacy systems.\n- **Not testing SIEM integration in PoC**: TIP value depends heavily on downstream integration quality; always test SIEM\u002FSOAR connectivity during evaluation.\n",{"name":5,"tags":25,"author":35,"domain":36,"source":37,"license":15,"version":38,"nist_csf":39,"subdomain":44,"description":45,"mitre_attack":46,"source_commit":51},[26,27,28,29,30,31,32,33,34],"TIP","ThreatConnect","MISP","OpenCTI","Anomali","EclecticIQ","STIX-TAXII","CTI-program","procurement","team-cybersecurity","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0.0",[40,41,42,43],"ID.RA-01","ID.RA-05","DE.CM-01","DE.AE-02","threat-intelligence","Evaluates and selects Threat Intelligence Platform (TIP) products based on organizational requirements including feed integration capability, STIX\u002FTAXII support, workflow automation, analyst interface, and total cost of ownership. Use when conducting a TIP procurement, migrating between TIP solutions, or assessing whether the current TIP meets program maturity requirements. Activates for requests involving ThreatConnect, MISP, OpenCTI, Anomali, EclecticIQ, or TIP procurement decisions.\n",[47,48,49,50],"T1591","T1592","T1593","T1589","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fevaluating-threat-intelligence-platforms",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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill evaluating-threat-intelligence-platforms",{"tool":68,"command":69},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill evaluating-threat-intelligence-platforms",{"tool":71,"command":72},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill evaluating-threat-intelligence-platforms","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fevaluating-threat-intelligence-platforms\u002FSKILL.md",true,[76,80,86],{"path":77,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fapi-reference.md","REFERENCE","参考文档",2780,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fevaluating-threat-intelligence-platforms\u002Freferences\u002Fapi-reference.md",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fagent.py","SCRIPT","脚本",9491,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fevaluating-threat-intelligence-platforms\u002Fscripts\u002Fagent.py",[93,101,108,116,124,132],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"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":133,"name":134,"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":135,"categories":136,"keywords":137,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]