[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE7Z4TQFMVA16KZGFQ8RKM":3,"skill-same:01M6AE7Z4TQFMVA16KZGFQ8RKM":119},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6AE7Z4TQFMVA16KZGFQ8RKM","deploying-osquery-for-endpoint-monitoring",null,"Deploys and configures osquery for real-time endpoint monitoring using SQL-based queries to inspect running processes, open ports, installed software, and system configuration. Use when building visibility into endpoint state, threat hunting across fleet, or implementing compliance monitoring. Activates for requests involving osquery deployment, endpoint visibility, fleet management, or SQL-based endpoint querying.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",36078,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeploying-osquery-for-endpoint-monitoring\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"monitoring","endpoint","deploying osquery for endpoint monitoring","security","cybersecurity","threat hunting","sql","pr","deployment","state","compliance","threat-hunting","endpoint-security","osquery","endpoint-monitoring","fleet-management","2026-11-10 10:12:30",false,"---\nname: deploying-osquery-for-endpoint-monitoring\ndescription: 'Deploys and configures osquery for real-time endpoint monitoring using\n  SQL-based queries to inspect running processes, open ports, installed software,\n  and system configuration. Use when building visibility into endpoint state, threat\n  hunting across fleet, or implementing compliance monitoring. Activates for requests\n  involving osquery deployment, endpoint visibility, fleet management, or SQL-based\n  endpoint querying.\n\n  '\ndomain: cybersecurity\nsubdomain: endpoint-security\ntags:\n- endpoint\n- osquery\n- endpoint-monitoring\n- threat-hunting\n- fleet-management\nmitre_attack:\n- T1547.001\n- T1053.005\n- T1543.003\n- T1057\n- T1071.001\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.PS-02\n- DE.CM-01\n- PR.IR-01\n---\n# Deploying Osquery for Endpoint Monitoring\n\n## When to Use\n\nUse this skill when:\n- Deploying osquery across Windows, macOS, and Linux endpoints for fleet-wide visibility\n- Building threat hunting queries using osquery's SQL interface\n- Monitoring endpoint compliance (installed software, open ports, running services)\n- Integrating osquery data with SIEM or Kolide\u002FFleet for centralized management\n\n**Do not use** for real-time alerting (osquery is periodic\u002Fon-demand; use EDR for real-time).\n\n## Prerequisites\n\n- Osquery package for target OS (https:\u002F\u002Fosquery.io\u002Fdownloads)\n- Fleet management server (Kolide Fleet or FleetDM) for enterprise deployment\n- TLS certificates for secure agent-to-server communication\n- Log aggregation pipeline (Filebeat, Fluentd) for osquery result logs\n\n## Workflow\n\n### Step 1: Install Osquery\n\n```bash\n# Ubuntu\u002FDebian\nexport OSQUERY_KEY=1484120AC4E9F8A1A577AEEE97A80C63C9D8B80B\napt-key adv --keyserver hkp:\u002F\u002Fkeyserver.ubuntu.com:80 --recv-keys $OSQUERY_KEY\nadd-apt-repository 'deb [arch=amd64] https:\u002F\u002Fpkg.osquery.io\u002Fdeb deb main'\napt-get update && apt-get install osquery -y\n\n# Windows (MSI)\n# Download from https:\u002F\u002Fosquery.io\u002Fdownloads\u002Fofficial\nmsiexec \u002Fi osquery-5.12.1.msi \u002Fquiet\n\n# macOS\nbrew install osquery\n```\n\n### Step 2: Configure Osquery\n\n```json\n\u002F\u002F \u002Fetc\u002Fosquery\u002Fosquery.conf (Linux\u002FmacOS) or C:\\ProgramData\\osquery\\osquery.conf\n{\n  \"options\": {\n    \"config_plugin\": \"filesystem\",\n    \"logger_plugin\": \"filesystem\",\n    \"logger_path\": \"\u002Fvar\u002Flog\u002Fosquery\",\n    \"disable_logging\": \"false\",\n    \"schedule_splay_percent\": \"10\",\n    \"events_expiry\": \"3600\",\n    \"verbose\": \"false\",\n    \"worker_threads\": \"2\",\n    \"enable_monitor\": \"true\",\n    \"disable_events\": \"false\",\n    \"disable_audit\": \"false\",\n    \"audit_allow_config\": \"true\",\n    \"host_identifier\": \"hostname\",\n    \"enable_syslog\": \"true\"\n  },\n  \"schedule\": {\n    \"process_monitor\": {\n      \"query\": \"SELECT pid, name, path, cmdline, uid, parent FROM processes WHERE on_disk = 0;\",\n      \"interval\": 300,\n      \"description\": \"Detect processes running without on-disk binary (fileless)\"\n    },\n    \"listening_ports\": {\n      \"query\": \"SELECT DISTINCT p.name, p.path, lp.port, lp.protocol, lp.address FROM listening_ports lp JOIN processes p ON lp.pid = p.pid WHERE lp.port != 0;\",\n      \"interval\": 600,\n      \"description\": \"Monitor listening network ports\"\n    },\n    \"persistence_check\": {\n      \"query\": \"SELECT name, path, source FROM startup_items;\",\n      \"interval\": 3600,\n      \"description\": \"Monitor persistence mechanisms\"\n    },\n    \"installed_packages\": {\n      \"query\": \"SELECT name, version, source FROM deb_packages;\",\n      \"interval\": 86400,\n      \"description\": \"Daily software inventory\"\n    },\n    \"users_and_groups\": {\n      \"query\": \"SELECT u.username, u.uid, u.gid, u.shell, u.directory FROM users u WHERE u.uid >= 1000;\",\n      \"interval\": 3600\n    },\n    \"crontab_monitor\": {\n      \"query\": \"SELECT * FROM crontab;\",\n      \"interval\": 3600,\n      \"description\": \"Monitor scheduled tasks\"\n    },\n    \"suid_binaries\": {\n      \"query\": \"SELECT path, username, permissions FROM suid_bin;\",\n      \"interval\": 86400,\n      \"description\": \"Detect SUID binaries\"\n    }\n  },\n  \"packs\": {\n    \"incident-response\": \"\u002Fusr\u002Fshare\u002Fosquery\u002Fpacks\u002Fincident-response.conf\",\n    \"ossec-rootkit\": \"\u002Fusr\u002Fshare\u002Fosquery\u002Fpacks\u002Fossec-rootkit.conf\",\n    \"vuln-management\": \"\u002Fusr\u002Fshare\u002Fosquery\u002Fpacks\u002Fvuln-management.conf\"\n  }\n}\n```\n\n### Step 3: Threat Hunting Queries\n\n```sql\n-- Detect processes with no on-disk binary (potential fileless malware)\nSELECT pid, name, path, cmdline FROM processes WHERE on_disk = 0;\n\n-- Find listening ports not associated with known services\nSELECT lp.port, lp.protocol, p.name, p.path\nFROM listening_ports lp JOIN processes p ON lp.pid = p.pid\nWHERE lp.port NOT IN (22, 80, 443, 3306, 5432);\n\n-- Detect unauthorized SSH keys\nSELECT * FROM authorized_keys WHERE NOT key LIKE '%admin-team%';\n\n-- Find recently modified system binaries\nSELECT path, mtime, size FROM file\nWHERE path LIKE '\u002Fusr\u002Fbin\u002F%' AND mtime > (strftime('%s', 'now') - 86400);\n\n-- Detect processes connecting to external IPs\nSELECT DISTINCT p.name, p.path, pn.remote_address, pn.remote_port\nFROM process_open_sockets pn JOIN processes p ON pn.pid = p.pid\nWHERE pn.remote_address NOT LIKE '10.%'\n  AND pn.remote_address NOT LIKE '172.16.%'\n  AND pn.remote_address NOT LIKE '192.168.%'\n  AND pn.remote_address != '127.0.0.1'\n  AND pn.remote_address != '0.0.0.0';\n\n-- Windows: Detect unsigned running executables\nSELECT p.name, p.path, a.result AS signature_status\nFROM processes p JOIN authenticode a ON p.path = a.path\nWHERE a.result != 'trusted';\n```\n\n### Step 4: Deploy FleetDM for Centralized Management\n\n```bash\n# FleetDM provides centralized osquery management\n# Deploy FleetDM server, configure agents to report to it\n# Agents use TLS enrollment and config from Fleet\n\n# Agent configuration for Fleet:\n# --tls_hostname=fleet.corp.com\n# --tls_server_certs=\u002Fetc\u002Fosquery\u002Ffleet.pem\n# --enroll_secret_path=\u002Fetc\u002Fosquery\u002Fenroll_secret\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Osquery** | Open-source endpoint agent that exposes OS state as SQL tables for querying |\n| **Schedule** | Periodic queries that run at defined intervals and log results |\n| **Pack** | Collection of related queries grouped for specific use cases (IR, compliance) |\n| **FleetDM** | Open-source osquery fleet management platform |\n| **Differential Results** | Osquery logs only changes between query executions, reducing data volume |\n\n## Tools & Systems\n\n- **Osquery**: https:\u002F\u002Fosquery.io\u002F - endpoint visibility agent\n- **FleetDM**: https:\u002F\u002Ffleetdm.com\u002F - centralized fleet management\n- **Kolide**: Cloud-based osquery management with Slack integration\n- **osquery-go**: Go client library for osquery extensions\n\n## Common Pitfalls\n\n- **Query performance**: Complex queries with large table scans impact endpoint performance. Use WHERE clauses and test query cost with `EXPLAIN`.\n- **Schedule intervals too aggressive**: Running heavy queries every 60 seconds causes CPU spikes. Use 300-3600 second intervals for most queries.\n- **Not using differential mode**: Without differential logging, osquery logs all results every interval. Differential mode logs only changes.\n- **Missing event tables**: Some osquery tables require events framework enabled (process_events, socket_events). Enable with `--disable_events=false`.\n","# Deploying Osquery for Endpoint Monitoring\n\n## When to Use\n\nUse this skill when:\n- Deploying osquery across Windows, macOS, and Linux endpoints for fleet-wide visibility\n- Building threat hunting queries using osquery's SQL interface\n- Monitoring endpoint compliance (installed software, open ports, running services)\n- Integrating osquery data with SIEM or Kolide\u002FFleet for centralized management\n\n**Do not use** for real-time alerting (osquery is periodic\u002Fon-demand; use EDR for real-time).\n\n## Prerequisites\n\n- Osquery package for target OS (https:\u002F\u002Fosquery.io\u002Fdownloads)\n- Fleet management server (Kolide Fleet or FleetDM) for enterprise deployment\n- TLS certificates for secure agent-to-server communication\n- Log aggregation pipeline (Filebeat, Fluentd) for osquery result logs\n\n## Workflow\n\n### Step 1: Install Osquery\n\n```bash\n# Ubuntu\u002FDebian\nexport OSQUERY_KEY=1484120AC4E9F8A1A577AEEE97A80C63C9D8B80B\napt-key adv --keyserver hkp:\u002F\u002Fkeyserver.ubuntu.com:80 --recv-keys $OSQUERY_KEY\nadd-apt-repository 'deb [arch=amd64] https:\u002F\u002Fpkg.osquery.io\u002Fdeb deb main'\napt-get update && apt-get install osquery -y\n\n# Windows (MSI)\n# Download from https:\u002F\u002Fosquery.io\u002Fdownloads\u002Fofficial\nmsiexec \u002Fi osquery-5.12.1.msi \u002Fquiet\n\n# macOS\nbrew install osquery\n```\n\n### Step 2: Configure Osquery\n\n```json\n\u002F\u002F \u002Fetc\u002Fosquery\u002Fosquery.conf (Linux\u002FmacOS) or C:\\ProgramData\\osquery\\osquery.conf\n{\n  \"options\": {\n    \"config_plugin\": \"filesystem\",\n    \"logger_plugin\": \"filesystem\",\n    \"logger_path\": \"\u002Fvar\u002Flog\u002Fosquery\",\n    \"disable_logging\": \"false\",\n    \"schedule_splay_percent\": \"10\",\n    \"events_expiry\": \"3600\",\n    \"verbose\": \"false\",\n    \"worker_threads\": \"2\",\n    \"enable_monitor\": \"true\",\n    \"disable_events\": \"false\",\n    \"disable_audit\": \"false\",\n    \"audit_allow_config\": \"true\",\n    \"host_identifier\": \"hostname\",\n    \"enable_syslog\": \"true\"\n  },\n  \"schedule\": {\n    \"process_monitor\": {\n      \"query\": \"SELECT pid, name, path, cmdline, uid, parent FROM processes WHERE on_disk = 0;\",\n      \"interval\": 300,\n      \"description\": \"Detect processes running without on-disk binary (fileless)\"\n    },\n    \"listening_ports\": {\n      \"query\": \"SELECT DISTINCT p.name, p.path, lp.port, lp.protocol, lp.address FROM listening_ports lp JOIN processes p ON lp.pid = p.pid WHERE lp.port != 0;\",\n      \"interval\": 600,\n      \"description\": \"Monitor listening network ports\"\n    },\n    \"persistence_check\": {\n      \"query\": \"SELECT name, path, source FROM startup_items;\",\n      \"interval\": 3600,\n      \"description\": \"Monitor persistence mechanisms\"\n    },\n    \"installed_packages\": {\n      \"query\": \"SELECT name, version, source FROM deb_packages;\",\n      \"interval\": 86400,\n      \"description\": \"Daily software inventory\"\n    },\n    \"users_and_groups\": {\n      \"query\": \"SELECT u.username, u.uid, u.gid, u.shell, u.directory FROM users u WHERE u.uid >= 1000;\",\n      \"interval\": 3600\n    },\n    \"crontab_monitor\": {\n      \"query\": \"SELECT * FROM crontab;\",\n      \"interval\": 3600,\n      \"description\": \"Monitor scheduled tasks\"\n    },\n    \"suid_binaries\": {\n      \"query\": \"SELECT path, username, permissions FROM suid_bin;\",\n      \"interval\": 86400,\n      \"description\": \"Detect SUID binaries\"\n    }\n  },\n  \"packs\": {\n    \"incident-response\": \"\u002Fusr\u002Fshare\u002Fosquery\u002Fpacks\u002Fincident-response.conf\",\n    \"ossec-rootkit\": \"\u002Fusr\u002Fshare\u002Fosquery\u002Fpacks\u002Fossec-rootkit.conf\",\n    \"vuln-management\": \"\u002Fusr\u002Fshare\u002Fosquery\u002Fpacks\u002Fvuln-management.conf\"\n  }\n}\n```\n\n### Step 3: Threat Hunting Queries\n\n```sql\n-- Detect processes with no on-disk binary (potential fileless malware)\nSELECT pid, name, path, cmdline FROM processes WHERE on_disk = 0;\n\n-- Find listening ports not associated with known services\nSELECT lp.port, lp.protocol, p.name, p.path\nFROM listening_ports lp JOIN processes p ON lp.pid = p.pid\nWHERE lp.port NOT IN (22, 80, 443, 3306, 5432);\n\n-- Detect unauthorized SSH keys\nSELECT * FROM authorized_keys WHERE NOT key LIKE '%admin-team%';\n\n-- Find recently modified system binaries\nSELECT path, mtime, size FROM file\nWHERE path LIKE '\u002Fusr\u002Fbin\u002F%' AND mtime > (strftime('%s', 'now') - 86400);\n\n-- Detect processes connecting to external IPs\nSELECT DISTINCT p.name, p.path, pn.remote_address, pn.remote_port\nFROM process_open_sockets pn JOIN processes p ON pn.pid = p.pid\nWHERE pn.remote_address NOT LIKE '10.%'\n  AND pn.remote_address NOT LIKE '172.16.%'\n  AND pn.remote_address NOT LIKE '192.168.%'\n  AND pn.remote_address != '127.0.0.1'\n  AND pn.remote_address != '0.0.0.0';\n\n-- Windows: Detect unsigned running executables\nSELECT p.name, p.path, a.result AS signature_status\nFROM processes p JOIN authenticode a ON p.path = a.path\nWHERE a.result != 'trusted';\n```\n\n### Step 4: Deploy FleetDM for Centralized Management\n\n```bash\n# FleetDM provides centralized osquery management\n# Deploy FleetDM server, configure agents to report to it\n# Agents use TLS enrollment and config from Fleet\n\n# Agent configuration for Fleet:\n# --tls_hostname=fleet.corp.com\n# --tls_server_certs=\u002Fetc\u002Fosquery\u002Ffleet.pem\n# --enroll_secret_path=\u002Fetc\u002Fosquery\u002Fenroll_secret\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Osquery** | Open-source endpoint agent that exposes OS state as SQL tables for querying |\n| **Schedule** | Periodic queries that run at defined intervals and log results |\n| **Pack** | Collection of related queries grouped for specific use cases (IR, compliance) |\n| **FleetDM** | Open-source osquery fleet management platform |\n| **Differential Results** | Osquery logs only changes between query executions, reducing data volume |\n\n## Tools & Systems\n\n- **Osquery**: https:\u002F\u002Fosquery.io\u002F - endpoint visibility agent\n- **FleetDM**: https:\u002F\u002Ffleetdm.com\u002F - centralized fleet management\n- **Kolide**: Cloud-based osquery management with Slack integration\n- **osquery-go**: Go client library for osquery extensions\n\n## Common Pitfalls\n\n- **Query performance**: Complex queries with large table scans impact endpoint performance. Use WHERE clauses and test query cost with `EXPLAIN`.\n- **Schedule intervals too aggressive**: Running heavy queries every 60 seconds causes CPU spikes. Use 300-3600 second intervals for most queries.\n- **Not using differential mode**: Without differential logging, osquery logs all results every interval. Differential mode logs only changes.\n- **Missing event tables**: Some osquery tables require events framework enabled (process_events, socket_events). Enable with `--disable_events=false`.\n",{"name":5,"tags":45,"author":46,"domain":28,"license":15,"version":47,"nist_csf":48,"subdomain":36,"description":53,"mitre_attack":54},[25,37,38,35,39],"mahipal","1.0.0",[49,50,51,52],"PR.PS-01","PR.PS-02","DE.CM-01","PR.IR-01","Deploys and configures osquery for real-time endpoint monitoring using SQL-based queries to inspect running processes, open ports, installed software, and system configuration. Use when building visibility into endpoint state, threat hunting across fleet, or implementing compliance monitoring. Activates for requests involving osquery deployment, endpoint visibility, fleet management, or SQL-based endpoint querying.\n",[55,56,57,58,59],"T1547.001","T1053.005","T1543.003","T1057","T1071.001","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fdeploying-osquery-for-endpoint-monitoring",4414,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill deploying-osquery-for-endpoint-monitoring",{"tool":76,"command":77},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill deploying-osquery-for-endpoint-monitoring",{"tool":79,"command":80},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill deploying-osquery-for-endpoint-monitoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeploying-osquery-for-endpoint-monitoring\u002FSKILL.md",true,[84,90,95,101,105,109,115],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"assets\u002Ftemplate.md","ASSET","资产文件",591,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeploying-osquery-for-endpoint-monitoring\u002Fassets\u002Ftemplate.md",{"path":91,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeploying-osquery-for-endpoint-monitoring\u002FLICENSE",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fapi-reference.md","REFERENCE","参考文档",1430,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeploying-osquery-for-endpoint-monitoring\u002Freferences\u002Fapi-reference.md",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fstandards.md",437,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeploying-osquery-for-endpoint-monitoring\u002Freferences\u002Fstandards.md",{"path":106,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fworkflows.md",622,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeploying-osquery-for-endpoint-monitoring\u002Freferences\u002Fworkflows.md",{"path":110,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fagent.py","SCRIPT","脚本",4422,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeploying-osquery-for-endpoint-monitoring\u002Fscripts\u002Fagent.py",{"path":116,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fprocess.py",2782,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdeploying-osquery-for-endpoint-monitoring\u002Fscripts\u002Fprocess.py",[120,145,169,196,222,249],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":127,"publishedAt":40},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[126],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[128,129,130,131,27,28,132,133,31,134,135,136,137,138,139,140,141,142,143,144],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","incident response","identity","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":146,"name":147,"nameZh":6,"description":148,"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":152,"publishedAt":40},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[151],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[153,141,154,155,27,156,28,31,157,158,159,160,161,162,163,164,165,166,167,168],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":179,"publishedAt":40},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[175,178],{"categoryNo":176,"categoryName":177,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[163,180,181,182,183,28,184,185,157,34,186,187,188,189,190,191,192,193,194,195],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","validation","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":203,"publishedAt":40},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[202],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[204,205,206,28,207,208,209,210,211,212,213,214,215,216,217,218,160,219,220,221],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":229,"publishedAt":40},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[228],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[230,231,232,28,233,234,235,236,237,238,239,240,241,242,243,244,245,246,247,248],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":253,"categories":254,"keywords":256,"publishedAt":40},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[255],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[27,257,28,258,259,260,261,262,263,264,265,191,266,192,267,268,269,270,271,272],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]