[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HKN0K08WACCCD3STWDK7EY":3,"skill-same:01M6HKN0K08WACCCD3STWDK7EY":122},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":68,"repositoryHtmlUrl":69,"repositoryHomepageUrl":6,"ownerHtmlUrl":70,"ownerBlogUrl":6,"ownerDescription":71,"updatedAt":72,"install":73,"resources":86},"01M6HKN0K08WACCCD3STWDK7EY","hardening-docker-containers-for-production",null,"Hardening Docker containers for production involves applying security best practices aligned with CIS Docker Benchmark v1.8.0 to minimize attack surface, prevent privilege escalation, and enforce leas","HenriqueMC17\u002Fagente-core","HenriqueMC17","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206460478?v=4","01M6HB63HBBF18AC4H09XTB549","Henrique Monteiro Cardoso","01M6HB63NGSQXWKWCFWW2B20W0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fhardening-docker-containers-for-production\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"docker","for","hardening docker containers for production","Production","hardening","containers","container-security","best practices","pr","escalation","cybersecurity","PS","container","cis","cm","enforce","id","de","with","v1","2026-11-10 10:12:30",false,"---\nname: hardening-docker-containers-for-production\ndescription: Hardening Docker containers for production involves applying security best practices aligned with CIS Docker Benchmark v1.8.0 to minimize attack surface, prevent privilege escalation, and enforce leas\ndomain: cybersecurity\nsubdomain: container-security\ntags:\n- containers\n- docker\n- security\n- hardening\n- CIS-benchmark\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.IR-01\n- ID.AM-08\n- DE.CM-01\nmitre_attack:\n- T1610\n- T1611\n- T1609\n- T1525\n- T1068\ncategory: hardening-docker-containers-for-production\n---\n# Hardening Docker Containers for Production\n\n## Overview\n\nHardening Docker containers for production involves applying security best practices aligned with CIS Docker Benchmark v1.8.0 to minimize attack surface, prevent privilege escalation, and enforce least-privilege principles across Docker daemon, images, containers, and runtime configurations.\n\n\n## When to Use\n\n- When deploying or configuring hardening docker containers for production 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- Docker Engine 24.0+ installed\n- Docker Compose v2\n- Linux host with kernel 5.10+\n- Root or sudo access on Docker host\n- docker-bench-security tool\n- Hadolint for Dockerfile linting\n- Dockle for image linting\n\n## Core Concepts\n\n### CIS Docker Benchmark Sections\n\n1. **Host Configuration** - Audit Docker daemon files, restrict access to \u002Fvar\u002Frun\u002Fdocker.sock\n2. **Docker Daemon Configuration** - Enable TLS, restrict inter-container communication, configure logging\n3. **Docker Daemon Configuration Files** - Set ownership and permissions on daemon.json\n4. **Container Images and Build File** - Use trusted base images, scan for vulnerabilities, multi-stage builds\n5. **Container Runtime** - Drop capabilities, read-only rootfs, restrict syscalls\n6. **Docker Security Operations** - Monitor, audit, and rotate credentials\n\n### Key Hardening Principles\n\n- **Least Privilege**: Run containers as non-root, drop all capabilities except required\n- **Immutability**: Use read-only root filesystem, tmpfs for writable directories\n- **Minimalism**: Use distroless or Alpine base images, multi-stage builds\n- **Isolation**: Apply seccomp profiles, AppArmor\u002FSELinux, namespace restrictions\n- **Auditability**: Enable content trust, log all container activity\n\n## Workflow\n\n### Step 1: Harden the Dockerfile\n\n```dockerfile\n# Use specific digest for reproducibility\nFROM python:3.12-slim@sha256:abc123... AS builder\n\nWORKDIR \u002Fapp\nCOPY requirements.txt .\nRUN pip install --no-cache-dir --user -r requirements.txt\n\n# Production stage - minimal image\nFROM gcr.io\u002Fdistroless\u002Fpython3-debian12\n\n# Copy only necessary artifacts\nCOPY --from=builder \u002Froot\u002F.local \u002Froot\u002F.local\nCOPY --from=builder \u002Fapp \u002Fapp\n\nWORKDIR \u002Fapp\n\n# Create non-root user\nUSER 65534:65534\n\n# Set read-only filesystem expectation\nLABEL org.opencontainers.image.source=\"https:\u002F\u002Fgithub.com\u002Forg\u002Fapp\"\n\nENTRYPOINT [\"python\", \"app.py\"]\n```\n\n### Step 2: Harden Docker Daemon Configuration\n\n```json\n{\n  \"icc\": false,\n  \"log-driver\": \"json-file\",\n  \"log-opts\": {\n    \"max-size\": \"10m\",\n    \"max-file\": \"3\"\n  },\n  \"live-restore\": true,\n  \"userland-proxy\": false,\n  \"no-new-privileges\": true,\n  \"default-ulimits\": {\n    \"nofile\": {\n      \"Name\": \"nofile\",\n      \"Hard\": 64000,\n      \"Soft\": 64000\n    },\n    \"nproc\": {\n      \"Name\": \"nproc\",\n      \"Hard\": 1024,\n      \"Soft\": 1024\n    }\n  },\n  \"seccomp-profile\": \"\u002Fetc\u002Fdocker\u002Fseccomp-default.json\",\n  \"tls\": true,\n  \"tlscacert\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fca.pem\",\n  \"tlscert\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fserver-cert.pem\",\n  \"tlskey\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fserver-key.pem\",\n  \"tlsverify\": true\n}\n```\n\n### Step 3: Harden Container Runtime\n\n```bash\ndocker run -d \\\n  --name production-app \\\n  --read-only \\\n  --tmpfs \u002Ftmp:rw,noexec,nosuid,size=100m \\\n  --tmpfs \u002Fvar\u002Frun:rw,noexec,nosuid,size=10m \\\n  --cap-drop ALL \\\n  --cap-add NET_BIND_SERVICE \\\n  --security-opt no-new-privileges:true \\\n  --security-opt seccomp=\u002Fetc\u002Fdocker\u002Fseccomp-default.json \\\n  --security-opt apparmor=docker-default \\\n  --pids-limit 100 \\\n  --memory 512m \\\n  --memory-swap 512m \\\n  --cpus 1.0 \\\n  --user 65534:65534 \\\n  --network custom-bridge \\\n  --restart on-failure:3 \\\n  --health-cmd \"curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth || exit 1\" \\\n  --health-interval 30s \\\n  --health-timeout 10s \\\n  --health-retries 3 \\\n  myapp:latest\n```\n\n### Step 4: Enable Docker Content Trust\n\n```bash\nexport DOCKER_CONTENT_TRUST=1\nexport DOCKER_CONTENT_TRUST_SERVER=https:\u002F\u002Fnotary.example.com\n\n# Sign and push image\ndocker trust sign myregistry.com\u002Fmyapp:v1.0.0\n\n# Verify image signature before pull\ndocker trust inspect --pretty myregistry.com\u002Fmyapp:v1.0.0\n```\n\n### Step 5: Configure Host-Level Auditing\n\n```bash\n# Add audit rules for Docker files and directories\ncat >> \u002Fetc\u002Faudit\u002Frules.d\u002Fdocker.rules \u003C\u003C 'EOF'\n-w \u002Fusr\u002Fbin\u002Fdocker -k docker\n-w \u002Fvar\u002Flib\u002Fdocker -k docker\n-w \u002Fetc\u002Fdocker -k docker\n-w \u002Flib\u002Fsystemd\u002Fsystem\u002Fdocker.service -k docker\n-w \u002Flib\u002Fsystemd\u002Fsystem\u002Fdocker.socket -k docker\n-w \u002Fetc\u002Fdefault\u002Fdocker -k docker\n-w \u002Fetc\u002Fdocker\u002Fdaemon.json -k docker\n-w \u002Fusr\u002Fbin\u002Fcontainerd -k docker\n-w \u002Fusr\u002Fbin\u002Frunc -k docker\nEOF\n\nsystemctl restart auditd\n```\n\n## Validation Commands\n\n```bash\n# Run Docker Bench Security\ndocker run --rm --net host --pid host \\\n  --userns host --cap-add audit_control \\\n  -e DOCKER_CONTENT_TRUST=$DOCKER_CONTENT_TRUST \\\n  -v \u002Fetc:\u002Fetc:ro \\\n  -v \u002Fusr\u002Fbin\u002Fcontainerd:\u002Fusr\u002Fbin\u002Fcontainerd:ro \\\n  -v \u002Fusr\u002Fbin\u002Frunc:\u002Fusr\u002Fbin\u002Frunc:ro \\\n  -v \u002Fusr\u002Flib\u002Fsystemd:\u002Fusr\u002Flib\u002Fsystemd:ro \\\n  -v \u002Fvar\u002Flib:\u002Fvar\u002Flib:ro \\\n  -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro \\\n  docker\u002Fdocker-bench-security\n\n# Lint Dockerfile\nhadolint Dockerfile\n\n# Lint built image\ndockle myapp:latest\n\n# Verify no containers running as root\ndocker ps -q | xargs docker inspect --format '{{.Id}}: User={{.Config.User}}'\n```\n\n## Key Security Controls\n\n| Control | Implementation | CIS Section |\n|---------|---------------|-------------|\n| Non-root user | USER instruction in Dockerfile | 4.1 |\n| Read-only rootfs | --read-only flag | 5.12 |\n| Drop capabilities | --cap-drop ALL | 5.3 |\n| Resource limits | --memory, --cpus, --pids-limit | 5.10 |\n| No new privileges | --security-opt no-new-privileges | 5.25 |\n| Content trust | DOCKER_CONTENT_TRUST=1 | 4.5 |\n| TLS for daemon | daemon.json TLS config | 2.6 |\n| Audit logging | auditd rules | 1.1 |\n\n## References\n\n- [CIS Docker Benchmark](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fdocker)\n- [Docker Security Best Practices](https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Fsecurity\u002F)\n- [Docker Bench Security Tool](https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdocker-bench-security)\n- [Hadolint - Dockerfile Linter](https:\u002F\u002Fgithub.com\u002Fhadolint\u002Fhadolint)\n","# Hardening Docker Containers for Production\n\n## Overview\n\nHardening Docker containers for production involves applying security best practices aligned with CIS Docker Benchmark v1.8.0 to minimize attack surface, prevent privilege escalation, and enforce least-privilege principles across Docker daemon, images, containers, and runtime configurations.\n\n\n## When to Use\n\n- When deploying or configuring hardening docker containers for production 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- Docker Engine 24.0+ installed\n- Docker Compose v2\n- Linux host with kernel 5.10+\n- Root or sudo access on Docker host\n- docker-bench-security tool\n- Hadolint for Dockerfile linting\n- Dockle for image linting\n\n## Core Concepts\n\n### CIS Docker Benchmark Sections\n\n1. **Host Configuration** - Audit Docker daemon files, restrict access to \u002Fvar\u002Frun\u002Fdocker.sock\n2. **Docker Daemon Configuration** - Enable TLS, restrict inter-container communication, configure logging\n3. **Docker Daemon Configuration Files** - Set ownership and permissions on daemon.json\n4. **Container Images and Build File** - Use trusted base images, scan for vulnerabilities, multi-stage builds\n5. **Container Runtime** - Drop capabilities, read-only rootfs, restrict syscalls\n6. **Docker Security Operations** - Monitor, audit, and rotate credentials\n\n### Key Hardening Principles\n\n- **Least Privilege**: Run containers as non-root, drop all capabilities except required\n- **Immutability**: Use read-only root filesystem, tmpfs for writable directories\n- **Minimalism**: Use distroless or Alpine base images, multi-stage builds\n- **Isolation**: Apply seccomp profiles, AppArmor\u002FSELinux, namespace restrictions\n- **Auditability**: Enable content trust, log all container activity\n\n## Workflow\n\n### Step 1: Harden the Dockerfile\n\n```dockerfile\n# Use specific digest for reproducibility\nFROM python:3.12-slim@sha256:abc123... AS builder\n\nWORKDIR \u002Fapp\nCOPY requirements.txt .\nRUN pip install --no-cache-dir --user -r requirements.txt\n\n# Production stage - minimal image\nFROM gcr.io\u002Fdistroless\u002Fpython3-debian12\n\n# Copy only necessary artifacts\nCOPY --from=builder \u002Froot\u002F.local \u002Froot\u002F.local\nCOPY --from=builder \u002Fapp \u002Fapp\n\nWORKDIR \u002Fapp\n\n# Create non-root user\nUSER 65534:65534\n\n# Set read-only filesystem expectation\nLABEL org.opencontainers.image.source=\"https:\u002F\u002Fgithub.com\u002Forg\u002Fapp\"\n\nENTRYPOINT [\"python\", \"app.py\"]\n```\n\n### Step 2: Harden Docker Daemon Configuration\n\n```json\n{\n  \"icc\": false,\n  \"log-driver\": \"json-file\",\n  \"log-opts\": {\n    \"max-size\": \"10m\",\n    \"max-file\": \"3\"\n  },\n  \"live-restore\": true,\n  \"userland-proxy\": false,\n  \"no-new-privileges\": true,\n  \"default-ulimits\": {\n    \"nofile\": {\n      \"Name\": \"nofile\",\n      \"Hard\": 64000,\n      \"Soft\": 64000\n    },\n    \"nproc\": {\n      \"Name\": \"nproc\",\n      \"Hard\": 1024,\n      \"Soft\": 1024\n    }\n  },\n  \"seccomp-profile\": \"\u002Fetc\u002Fdocker\u002Fseccomp-default.json\",\n  \"tls\": true,\n  \"tlscacert\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fca.pem\",\n  \"tlscert\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fserver-cert.pem\",\n  \"tlskey\": \"\u002Fetc\u002Fdocker\u002Ftls\u002Fserver-key.pem\",\n  \"tlsverify\": true\n}\n```\n\n### Step 3: Harden Container Runtime\n\n```bash\ndocker run -d \\\n  --name production-app \\\n  --read-only \\\n  --tmpfs \u002Ftmp:rw,noexec,nosuid,size=100m \\\n  --tmpfs \u002Fvar\u002Frun:rw,noexec,nosuid,size=10m \\\n  --cap-drop ALL \\\n  --cap-add NET_BIND_SERVICE \\\n  --security-opt no-new-privileges:true \\\n  --security-opt seccomp=\u002Fetc\u002Fdocker\u002Fseccomp-default.json \\\n  --security-opt apparmor=docker-default \\\n  --pids-limit 100 \\\n  --memory 512m \\\n  --memory-swap 512m \\\n  --cpus 1.0 \\\n  --user 65534:65534 \\\n  --network custom-bridge \\\n  --restart on-failure:3 \\\n  --health-cmd \"curl -f http:\u002F\u002Flocalhost:8080\u002Fhealth || exit 1\" \\\n  --health-interval 30s \\\n  --health-timeout 10s \\\n  --health-retries 3 \\\n  myapp:latest\n```\n\n### Step 4: Enable Docker Content Trust\n\n```bash\nexport DOCKER_CONTENT_TRUST=1\nexport DOCKER_CONTENT_TRUST_SERVER=https:\u002F\u002Fnotary.example.com\n\n# Sign and push image\ndocker trust sign myregistry.com\u002Fmyapp:v1.0.0\n\n# Verify image signature before pull\ndocker trust inspect --pretty myregistry.com\u002Fmyapp:v1.0.0\n```\n\n### Step 5: Configure Host-Level Auditing\n\n```bash\n# Add audit rules for Docker files and directories\ncat >> \u002Fetc\u002Faudit\u002Frules.d\u002Fdocker.rules \u003C\u003C 'EOF'\n-w \u002Fusr\u002Fbin\u002Fdocker -k docker\n-w \u002Fvar\u002Flib\u002Fdocker -k docker\n-w \u002Fetc\u002Fdocker -k docker\n-w \u002Flib\u002Fsystemd\u002Fsystem\u002Fdocker.service -k docker\n-w \u002Flib\u002Fsystemd\u002Fsystem\u002Fdocker.socket -k docker\n-w \u002Fetc\u002Fdefault\u002Fdocker -k docker\n-w \u002Fetc\u002Fdocker\u002Fdaemon.json -k docker\n-w \u002Fusr\u002Fbin\u002Fcontainerd -k docker\n-w \u002Fusr\u002Fbin\u002Frunc -k docker\nEOF\n\nsystemctl restart auditd\n```\n\n## Validation Commands\n\n```bash\n# Run Docker Bench Security\ndocker run --rm --net host --pid host \\\n  --userns host --cap-add audit_control \\\n  -e DOCKER_CONTENT_TRUST=$DOCKER_CONTENT_TRUST \\\n  -v \u002Fetc:\u002Fetc:ro \\\n  -v \u002Fusr\u002Fbin\u002Fcontainerd:\u002Fusr\u002Fbin\u002Fcontainerd:ro \\\n  -v \u002Fusr\u002Fbin\u002Frunc:\u002Fusr\u002Fbin\u002Frunc:ro \\\n  -v \u002Fusr\u002Flib\u002Fsystemd:\u002Fusr\u002Flib\u002Fsystemd:ro \\\n  -v \u002Fvar\u002Flib:\u002Fvar\u002Flib:ro \\\n  -v \u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro \\\n  docker\u002Fdocker-bench-security\n\n# Lint Dockerfile\nhadolint Dockerfile\n\n# Lint built image\ndockle myapp:latest\n\n# Verify no containers running as root\ndocker ps -q | xargs docker inspect --format '{{.Id}}: User={{.Config.User}}'\n```\n\n## Key Security Controls\n\n| Control | Implementation | CIS Section |\n|---------|---------------|-------------|\n| Non-root user | USER instruction in Dockerfile | 4.1 |\n| Read-only rootfs | --read-only flag | 5.12 |\n| Drop capabilities | --cap-drop ALL | 5.3 |\n| Resource limits | --memory, --cpus, --pids-limit | 5.10 |\n| No new privileges | --security-opt no-new-privileges | 5.25 |\n| Content trust | DOCKER_CONTENT_TRUST=1 | 4.5 |\n| TLS for daemon | daemon.json TLS config | 2.6 |\n| Audit logging | auditd rules | 1.1 |\n\n## References\n\n- [CIS Docker Benchmark](https:\u002F\u002Fwww.cisecurity.org\u002Fbenchmark\u002Fdocker)\n- [Docker Security Best Practices](https:\u002F\u002Fdocs.docker.com\u002Fengine\u002Fsecurity\u002F)\n- [Docker Bench Security Tool](https:\u002F\u002Fgithub.com\u002Fdocker\u002Fdocker-bench-security)\n- [Hadolint - Dockerfile Linter](https:\u002F\u002Fgithub.com\u002Fhadolint\u002Fhadolint)\n",{"name":5,"tags":49,"author":52,"domain":34,"license":15,"version":53,"category":5,"nist_csf":54,"subdomain":30,"description":7,"mitre_attack":59},[29,24,50,28,51],"security","CIS-benchmark","mahipal","1.0",[55,56,57,58],"PR.PS-01","PR.IR-01","ID.AM-08","DE.CM-01",[60,61,62,63,64],"T1610","T1611","T1609","T1525","T1068","main","5eea5b3296f4673b5f481e8bcc1ba76281149f16","modules\u002Fhardening-docker-containers-for-production",0,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core","https:\u002F\u002Fgithub.com\u002FHenriqueMC17","Qualquer tecnologia suficientemente avançada é indistinguível da mágica.","2026-09-28 22:40:38",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add HenriqueMC17\u002Fagente-core --skill hardening-docker-containers-for-production",{"tool":79,"command":80},"bunx","bunx skills add HenriqueMC17\u002Fagente-core --skill hardening-docker-containers-for-production",{"tool":82,"command":83},"pnpm","pnpm dlx skills add HenriqueMC17\u002Fagente-core --skill hardening-docker-containers-for-production","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fhardening-docker-containers-for-production\u002FSKILL.md",true,[87,93,98,104,108,112,118],{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"assets\u002Ftemplate.md","ASSET","资产文件",2822,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fhardening-docker-containers-for-production\u002Fassets\u002Ftemplate.md",{"path":94,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fhardening-docker-containers-for-production\u002FLICENSE",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fapi-reference.md","REFERENCE","参考文档",1818,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fhardening-docker-containers-for-production\u002Freferences\u002Fapi-reference.md",{"path":105,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fstandards.md",3676,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fhardening-docker-containers-for-production\u002Freferences\u002Fstandards.md",{"path":109,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fworkflows.md",4344,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fhardening-docker-containers-for-production\u002Freferences\u002Fworkflows.md",{"path":113,"resourceType":114,"resourceTypeDesc":115,"sizeBytes":116,"sourceHtmlUrl":117},"scripts\u002Fagent.py","SCRIPT","脚本",5041,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fhardening-docker-containers-for-production\u002Fscripts\u002Fagent.py",{"path":119,"resourceType":114,"resourceTypeDesc":115,"sizeBytes":120,"sourceHtmlUrl":121},"scripts\u002Fprocess.py",15194,"https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fhardening-docker-containers-for-production\u002Fscripts\u002Fprocess.py",[123,151,176,198,214,233],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":132,"publishedAt":44},"01M6HPFF0RCN0X6WT5EBSV71GY","validating-backup-integrity-for-recovery","Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[129],{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[133,134,135,136,25,137,34,138,139,140,141,142,143,144,145,146,147,148,149,150],"integrity","backup","recovery","validating backup integrity for recovery","testing","validate","verification","hash-verification","incident-response","ransomware","detection","t1078","t1490","disaster-recovery","restore","incident","disaster recovery","ransomware response",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":44},"01M6HPFAWJVFK25Q33K3T7WQ8G","triaging-vulnerabilities-with-ssvc-framework","Triage and prioritize vulnerabilities using CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree framework to produce actionable remediation priorities.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[],[158,159,160,161,42,34,162,163,164,165,166,167,168,169,170,171,172,173,174,175],"vulnerabilities","framework","ssvc","triaging vulnerabilities with ssvc framework","triage and prioritize","CISA","vulnerability-management","risk-management","cvss","remediation","vulnerability","prioritization","decision-tree","prioritize","decision","priorities","actionable","tree",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":44},"01M6HPF6JS9X72WP59094H3ASQ","triaging-security-incident","Performs initial triage of security incidents to determine severity, scope, and required response actions using the NIST SP 800-61r3 and SANS PICERL frameworks. Classifies incidents by type, assigns priority based on business impact, and routes...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident\u002FSKILL.md",[],[50,183,148,34,184,185,186,144,145,187,188,189,190,191,192,193,194,195,196,197],"triaging security incident","actions","soc","NIST","analysis","severity-classification","incident-triage","SANS-PICERL","SOC-operations","picerl","conversion","isolation","scope","impact","consistency",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":44},"01M6HPF2EX6ZYNYYHKBRJN7GEF","triaging-security-incident-with-ir-playbook","Classify and prioritize security incidents using structured IR playbooks to determine severity, assign response teams, and initiate appropriate response procedures.","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-incident-with-ir-playbook\u002FSKILL.md",[],[50,205,206,183,148,42,34,207,185,141,208,209,144,145,210,188,171,211,212,213],"playbook","triaging security incident with ir playbook","teams","IR-playbook","severity","classification","classify","incidents","initiate",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":220,"publishedAt":44},"01M6HPEY9XPGE7X95AG4XJFQAW","triaging-security-alerts-in-splunk","Triages security alerts in Splunk Enterprise Security by classifying severity, investigating notable events, correlating related telemetry, and making escalation or closure decisions using SPL queries and the Incident Review dashboard. Use when...","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftriaging-security-alerts-in-splunk\u002FSKILL.md",[],[50,221,222,223,224,225,34,226,227,228,185,229,144,230,231,232,191,38,148,41],"security alerts","splunk","triaging security alerts in splunk","alerts","review","siem","dashboard","search","correlation-search","t1566","notable-events","incident-review",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":239,"publishedAt":44},"01M6HPET6XGEPEJPN7V032JGZ0","tracking-threat-actor-infrastructure","Threat actor infrastructure tracking involves monitoring and mapping adversary-controlled assets including command-and-control (C2) servers, phishing domains, exploit kit hosts, bulletproof hosting, a","https:\u002F\u002Fgithub.com\u002FHenriqueMC17\u002Fagente-core\u002Fblob\u002Fmain\u002Fmodules\u002Ftracking-threat-actor-infrastructure\u002FSKILL.md",[],[240,241,242,243,34,244,245,246,247,248,249,230,250,251,38,252,41,253,254,255],"infrastructure","tracking threat actor infrastructure","tracking","threat","monitoring","mitre-attack","threat-actor","threat-intelligence","command-and-control","dns","command","exploit","intelligence","domains","kit","hosts"]