[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71C6STBKD45G0RZ2WVV67HX":3,"skill-same:01M71C6STBKD45G0RZ2WVV67HX":56},{"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":18,"publishedAt":24,"linkOnly":25,"markdownContent":26,"markdownBody":27,"frontMatter":28,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M71C6STBKD45G0RZ2WVV67HX","cloud-devsecops-policy",null,"Cloud Devsecops Policy.","DCx7C5\u002Fai-marketplace","DCx7C5","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42419559?v=4","01M71C01G2AZV3NTNGWAWSHJPP","DC","01M71C01GQW6G50S2BYMS7PP3E",0,"MIT","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-devsecops-policy\u002FSKILL.md",[],[19,20,21,22,23],"devsecops","policy","cloud","cloud devsecops policy","cybersecurity","2026-11-10 10:12:30",false,"---\nname: cloud-devsecops-policy\ndescription: \"Cloud Devsecops Policy.\"\ndomain: cybersecurity\n---\n\n|\n| OPA | Open Policy Agent — general-purpose policy engine using Rego language for policy decisions |\n| Rego | OPA's declarative query language for writing policy rules |\n| Gatekeeper | Kubernetes-native OPA integration implementing admission control via ConstraintTemplates |\n| ConstraintTemplate | CRD defining the Rego policy logic and parameters schema for a class of constraints |\n| Constraint | Instance of a ConstraintTemplate with specific parameters and scope (which resources to check) |\n| Admission Controller | Kubernetes component that intercepts API requests before persistence and can allow or deny them |\n| conftest | CLI tool for testing structured data (YAML, JSON, HCL) against OPA policies |\n\n## Tools & Systems\n\n- **Open Policy Agent (OPA)**: General-purpose policy engine for unified policy enforcement\n- **Gatekeeper**: Kubernetes admission controller built on OPA with CRD-based configuration\n- **conftest**: Testing framework for OPA policies against configuration files\n- **Kyverno**: Alternative Kubernetes policy engine using YAML-based policies (no Rego required)\n- **Styra DAS**: Commercial OPA management platform with policy authoring, testing, and distribution\n\n## Common Scenarios\n\n### Scenario: Enforcing Container Security Standards Across Clusters\n\n**Context**: Multiple development teams deploy to shared Kubernetes clusters. Some teams run privileged containers and images without resource limits, causing security and stability issues.\n\n**Approach**:\n1. Deploy Gatekeeper on all clusters via GitOps (Helm chart in a FluxCD repository)\n2. Create ConstraintTemplates for: no privileged containers, required resource limits, required labels, no latest tag\n3. Start with `enforcementAction: warn` to identify violations without blocking deployments\n4. Notify teams of violations and provide a 2-week remediation window\n5. Switch to `enforcementAction: deny` after the remediation period\n6. Add `excludedNamespaces` for kube-system and monitoring namespaces\n\n**Pitfalls**: Deploying Gatekeeper with deny mode immediately can break existing workloads. Always start with warn mode. Overly restrictive policies without exemptions for system namespaces can prevent cluster components from functioning.\n\n## Output Format\n\n```\nOPA Policy Evaluation Report\n==============================\nCluster: production-east\nDate: 2026-02-23\nGatekeeper Version: 3.16.0\n\nCONSTRAINT SUMMARY:\n  K8sRequiredLabels:        12 violations (warn)\n  K8sBlockPrivileged:        0 violations (deny)\n  K8sContainerLimits:        8 violations (deny)\n  K8sBlockLatestTag:         3 violations (deny)\n\nBLOCKED DEPLOYMENTS (deny):\n  [K8sContainerLimits] deployment\u002Fapi-server in ns\u002Fpayments\n    - Container 'api' has no memory limit\n  [K8sBlockLatestTag] deployment\u002Ffrontend in ns\u002Fweb\n    - Container 'nginx' uses :latest tag\n\nAUDIT VIOLATIONS (warn):\n  [K8sRequiredLabels] namespace\u002Fstaging\n    - Missing labels: {cost-center}\n```\n","|\n| OPA | Open Policy Agent — general-purpose policy engine using Rego language for policy decisions |\n| Rego | OPA's declarative query language for writing policy rules |\n| Gatekeeper | Kubernetes-native OPA integration implementing admission control via ConstraintTemplates |\n| ConstraintTemplate | CRD defining the Rego policy logic and parameters schema for a class of constraints |\n| Constraint | Instance of a ConstraintTemplate with specific parameters and scope (which resources to check) |\n| Admission Controller | Kubernetes component that intercepts API requests before persistence and can allow or deny them |\n| conftest | CLI tool for testing structured data (YAML, JSON, HCL) against OPA policies |\n\n## Tools & Systems\n\n- **Open Policy Agent (OPA)**: General-purpose policy engine for unified policy enforcement\n- **Gatekeeper**: Kubernetes admission controller built on OPA with CRD-based configuration\n- **conftest**: Testing framework for OPA policies against configuration files\n- **Kyverno**: Alternative Kubernetes policy engine using YAML-based policies (no Rego required)\n- **Styra DAS**: Commercial OPA management platform with policy authoring, testing, and distribution\n\n## Common Scenarios\n\n### Scenario: Enforcing Container Security Standards Across Clusters\n\n**Context**: Multiple development teams deploy to shared Kubernetes clusters. Some teams run privileged containers and images without resource limits, causing security and stability issues.\n\n**Approach**:\n1. Deploy Gatekeeper on all clusters via GitOps (Helm chart in a FluxCD repository)\n2. Create ConstraintTemplates for: no privileged containers, required resource limits, required labels, no latest tag\n3. Start with `enforcementAction: warn` to identify violations without blocking deployments\n4. Notify teams of violations and provide a 2-week remediation window\n5. Switch to `enforcementAction: deny` after the remediation period\n6. Add `excludedNamespaces` for kube-system and monitoring namespaces\n\n**Pitfalls**: Deploying Gatekeeper with deny mode immediately can break existing workloads. Always start with warn mode. Overly restrictive policies without exemptions for system namespaces can prevent cluster components from functioning.\n\n## Output Format\n\n```\nOPA Policy Evaluation Report\n==============================\nCluster: production-east\nDate: 2026-02-23\nGatekeeper Version: 3.16.0\n\nCONSTRAINT SUMMARY:\n  K8sRequiredLabels:        12 violations (warn)\n  K8sBlockPrivileged:        0 violations (deny)\n  K8sContainerLimits:        8 violations (deny)\n  K8sBlockLatestTag:         3 violations (deny)\n\nBLOCKED DEPLOYMENTS (deny):\n  [K8sContainerLimits] deployment\u002Fapi-server in ns\u002Fpayments\n    - Container 'api' has no memory limit\n  [K8sBlockLatestTag] deployment\u002Ffrontend in ns\u002Fweb\n    - Container 'nginx' uses :latest tag\n\nAUDIT VIOLATIONS (warn):\n  [K8sRequiredLabels] namespace\u002Fstaging\n    - Missing labels: {cost-center}\n```\n",{"name":5,"domain":23,"description":7},"main","a91f1293287ffa9f4f1b8f486cd6e835a1568c84","skills\u002Fcloud-devsecops-policy","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace","https:\u002F\u002Fgithub.com\u002FDCx7C5","#Python","2026-09-01 11:21:00",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add DCx7C5\u002Fai-marketplace --skill cloud-devsecops-policy",{"tool":42,"command":43},"bunx","bunx skills add DCx7C5\u002Fai-marketplace --skill cloud-devsecops-policy",{"tool":45,"command":46},"pnpm","pnpm dlx skills add DCx7C5\u002Fai-marketplace --skill cloud-devsecops-policy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-devsecops-policy\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"index.json","REFERENCE","参考文档",488,"https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-devsecops-policy\u002Findex.json",[57,82,105,127,149,165],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":24},"01M71HAPZ01KQ30RKTB0FFSQ05","services-wmi-persistence-detect","Detect WMI event subscription persistence by enumerating ActiveScriptEventConsumer, CommandLineEventConsumer, and permanent subscriptions in the WMI repository.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fpersistence\u002Fdetect\u002FSKILL.md",[],[64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,23,81],"services","detect","services wmi persistence detect","wmi","persistence","de","cm","process","activescript","event","subscriptions","commandline-consumer","repository","subscription","event-subscription","t1546.003","forensics","process-forensics",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":24},"01M71HAK6JTTTS229T17WJMMCG","services-wmi-exec-exploit","Perform lateral movement across Windows networks using WMI-based remote execution techniques including Impacket wmiexec.py, CrackMapExec, and native WMI commands for stealthy post-exploitation during red team engagements.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fservices\u002Fwmi\u002Fexec\u002Fexploit\u002FSKILL.md",[],[89,64,90,67,91,92,93,23,94,95,96,97,98,99,69,100,101,102,103,104],"exploit","services wmi exec exploit","exec","remote","traffic","Bash","analysis","team","across","crackmapexec","native","command","lateral movement","read","lateral-movement","Impacket",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":24},"01M71HAG6MHKNQV8KDZKMT4886","registry-artifact-extract","Extract and analyze Windows Registry hives to uncover user activity, installed software, autostart entries, and evidence of system compromise.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fregistry\u002Fartifact\u002Fextract\u002FSKILL.md",[],[112,113,114,115,116,117,23,94,118,95,119,120,69,102,121,122,123,124,125,126],"artifact","registry","registry artifact extract","extract","evidence-collection","artifact-analysis","collection","analyze","uncover","software","activity","digital-forensics","windows-registry","regripper","sonnet",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":24},"01M71HACR4A8XTWTTSXK4124AA","processes-token-impersonate-detect","Detect Windows token impersonation and privilege abuse including SeImpersonatePrivilege exploitation via Potato attacks and token stealing techniques.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Ftoken\u002Fimpersonate\u002Fdetect\u002FSKILL.md",[],[65,134,135,136,137,138,139,70,140,23,81,141,142,143,144,145,146,147,148,69],"processes token impersonate detect","token","processes","attacks","windows","escalation","techniques","privilege-escalation","seimpersonate","token-impersonation","printspoofer","exploitation","potato","impersonation","via",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":24},"01M71HAABSB4Z6QFSXEG00R4RK","processes-thread-injection-detect","Detect Windows thread injection techniques including CreateRemoteThread, QueueUserAPC, NtCreateThreadEx, and thread hijacking via process memory analysis.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fthread\u002Finjection\u002Fdetect\u002FSKILL.md",[],[156,157,65,158,136,138,159,70,160,140,23,81,95,161,162,163,164,148,69,71],"thread","processes thread injection detect","injection","memory","process-injection","api","apc-injection","thread-injection","nt-api",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":24},"01M71HA7H311V5G14WMX58HQSS","processes-hollow-technique-detect","Detect process hollowing (RunPE) by identifying processes with mismatched image paths between PEB and VAD tree, or unmapped PE headers in memory.","https:\u002F\u002Fgithub.com\u002FDCx7C5\u002Fai-marketplace\u002Fblob\u002Fmain\u002Fskills\u002Fwindows\u002Fprocesses\u002Fhollow\u002Ftechnique\u002Fdetect\u002FSKILL.md",[],[172,65,136,173,159,70,174,175,23,81,176,177,178,179,180,181,69,71,182,183],"processes hollow technique detect","tree","memory-forensics","process-hollow","peb","runpe","image","pe-header","in memory","with","mismatched","headers"]