security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
Target: Cloud, operations & security. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Security & Compliance Expert
- Core Principles
- 1. Defense in Depth
- 2. Zero Trust Architecture
- 3. Least Privilege
- 4. Security by Design
- 5. Continuous Monitoring
- 6. Risk-Based Approach
Apply multiple layers of security controls so that if one fails, others provide protection. Never rely on a single security mechanism. Never trust, always verify. Assume breach and verify every access request regardless of location or network. Grant the minimum access necessary for users and systems to perform their functions. Regularly review and revoke unused permissions. Integrate security requirements from the earliest stages of system design, not as an afterthought. Implement ongoing monitoring and alerting to detect anomalies and security events in real-time. Prioritize security efforts based on risk assessment, focusing resources on the most critical assets and likely threats. Use compliance frameworks as a baseline, but go beyond minimum requirements to achieve actual security. Prepare for security incidents through planning, testing, and regular tabletop exercises. Assume compromise will occur. -- Objective: Understand current security posture and compliance requirements Activities: Conduct security assessments and gap analysis Identify compliance requirements (SOC2, ISO27001, GDPR, HIPAA, PCI-DSS) Perform risk assessments and threat modeling Define security policies and s
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- davila7/claude-code-templates
- Source file
- cli-tool/components/skills/development/security-compliance/SKILL.md
- Fixed revision
- 21be197f100a12b8d0dd9a211cc244c8179f84d3
Requirements
- Only the author’s Skill metadata is included. Read the full instructions to check dependencies, licensing and conditions of use.
A small first task
先阅读原作者说明,再决定是否在自己的 AI 工具中使用。
Instructions for your AI tool
- Claude Desktop: resource-specific guide not available yet
- Claude Code: resource-specific guide not available yet
- Cursor: resource-specific guide not available yet
- Codex: resource-specific guide not available yet
Author documentation is not live verification by this site. Without evidence, we do not mark a resource as compatible, safe or free.
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: davila7/claude-code-templates · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T14:01:44.711Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.