--- name: security-scanning-security-hardening-1e4daa1efdd2 description: "Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls." risk: unknown source: community date_added: "2026-02-27" --- Implement comprehensive security hardening with defense-in-depth strategy through coordinated multi-agent orchestration: [Extended thinking: This workflow implements a defense-in-depth security strategy across all application layers. It coordinates specialized security agents to perform comprehensive assessments, implement layered security controls, and establish continuous security monitoring. The approach follows modern DevSecOps principles with shift-left security, automated scanning, and compliance validation. Each phase builds upon previous findings to create a resilient security posture that addresses both current vulnerabilities and future threats.] ## Use this skill when - Running a coordinated security hardening program - Establishing defense-in-depth controls across app, infra, and CI/CD - Prioritizing remediation from scans and threat modeling ## Do not use this skill when - You only need a quick scan without remediation work - You lack authorization for security testing or changes - The environment cannot tolerate invasive security controls ## Instructions 1. Execute Phase 1 to establish a security baseline. 2. Apply Phase 2 remediations for high-risk issues. 3. Implement Phase 3 controls and validate defenses. 4. Complete Phase 4 validation and compliance checks. ## Safety - Avoid intrusive testing in production without approval. - Ensure rollback plans exist before hardening changes. ## Phase 1: Comprehensive Security Assessment ### 1. Initial Vulnerability Scanning - Use Task tool with subagent_type="security-auditor" - Prompt: "Perform comprehensive security assessment on: $ARGUMENTS. Execute SAST analysis with Semgrep/SonarQube, DAST scanning with OWASP ZAP, dependency audit with Snyk, secrets detection with GitLeaks/TruffleHog. Generate SBOM for supply chain analysis. Identify OWASP Top 10 vulnerabilities, CWE weaknesses, and CVE exposures." - Output: Detailed vulnerability report with CVSS scores, exploitability analysis, attack surface mapping, secrets exposure report, SBOM inventory - Context: Initial baseline for all remediation efforts ### 2. Threat Modeling and Risk Analysis - Use Task tool with subagent_type="security-auditor" - Prompt: "Conduct threat modeling using STRIDE methodology for: $ARGUMENTS. Analyze attack vectors, create attack trees, assess business impact of identified vulnerabilities. Map threats to MITRE ATT&CK framework. Prioritize risks based on likelihood and impact." - Output: Threat model diagrams, risk matrix with prioritized vulnerabilities, attack scenario documentation, business impact analysis - Context: Uses vulnerability scan results to inform threat priorities ### 3. Architecture Security Review - Use Task tool with subagent_type="backend-api-security::backend-architect" - Prompt: "Review architecture for security weaknesses in: $ARGUMENTS. Evaluate service boundaries, data flow security, authentication/authorization architecture, encryption implementation, network segmentation. Design zero-trust architecture patterns. Reference threat model and vulnerability findings." - Output: Security architecture assessment, zero-trust design recommendations, service mesh security requirements, data classification matrix - Context: Incorporates threat model to address architectural vulnerabilities ## Phase 2: Vulnerability Remediation ### 4. Critical Vulnerability Fixes - Use Task tool with subagent_type="security-auditor" - Prompt: "Coordinate immediate remediation of critical vulnerabilities (CVSS 7+) in: $ARGUMENTS. Fix SQL injections with parameterized queries, XSS with output encoding, authentication bypasses with secure session management, insecure deserialization with input validation. Apply security patches for CVEs." - Output: Patched code with vulnerability fixes, security patch documentation, regression test requirements - Context: Addresses high-priority items from vulnerability assessment ### 5. Backend Security Hardening - Use Task tool with subagent_type="backend-api-security::backend-security-coder" - Prompt: "Implement comprehensive backend security controls for: $ARGUMENTS. Add input validation with OWASP ESAPI, implement rate limiting and DDoS protection, secure API endpoints with OAuth2/JWT validation, add encryption for data at rest/transit using AES-256/TLS 1.3. Implement secure logging without PII exposure." - Output: Hardened API endpoints, validation middleware, encryption implementation, secure configuration templates - Context: Builds upon vulnerability fixes with preventive controls ### 6. Frontend Security Implementation - Use Task tool with subagent_type="frontend-mobile-security::frontend-security-coder" - Prompt: "Implement frontend security measures for: $ARGUMENTS. Configure CSP headers with nonce-based policies, implement XSS prevention with DOMPurify, secure authentication flows with PKCE OAuth2, add SRI for external resources, implement secure cookie handling with SameSite/HttpOnly/Secure flags." - Output: Secure frontend components, CSP policy configuration, authentication flow implementation, security headers configuration - Context: Complements backend security with client-side protections ### 7. Mobile Security Hardening - Use Task tool with subagent_type="frontend-mobile-security::mobile-security-coder" - Prompt: "Implement mobile app security for: $ARGUMENTS. Add certificate pinning, implement biometric authentication, secure local storage with encryption, obfuscate code with ProGuard/R8, implement anti-tampering and root/jailbreak detection, secure IPC communications." - Output: Hardened mobile application, security configuration files, obfuscation rules, certificate pinning implementation - Context: Extends security to mobile platforms if applicable ## Phase 3: Security Controls Implementation ### 8. Authentication and Authorization Enhancement - Use Task tool with subagent_type="security-auditor" - Prompt: "Implement modern authentication system for: $ARGUMENTS. Deploy OAuth2/OIDC with PKCE, implement MFA with TOTP/WebAuthn/FIDO2, add risk-based authentication, implement RBAC/ABAC with principle of least privilege, add session management with secure token rotation." - Output: Authentication service configuration, MFA implementation, authorization policies, session management system - Context: Strengthens access controls based on architecture review ### 9. Infrastructure Security Controls - Use Task tool with subagent_type="deployment-strategies::deployment-engineer" - Prompt: "Deploy infrastructure security controls for: $ARGUMENTS. Configure WAF rules for OWASP protection, implement network segmentation with micro-segmentation, deploy IDS/IPS systems, configure cloud security groups and NACLs, implement DDoS protection with rate limiting and geo-blocking." - Output: WAF configuration, network security policies, IDS/IPS rules, cloud security configurations - Context: Implements network-level defenses ### 10. Secrets Management Implementation - Use Task tool with subagent_type="deployment-strategies::deployment-engineer" - Prompt: "Implement enterprise secrets management for: $ARGUMENTS. Deploy HashiCorp Vault or AWS Secrets Manager, implement secret rotation policies, remove hardcoded secrets, configure least-privilege IAM roles, implement encryption key management with HSM support." - Output: Secrets management configuration, rotation policies, IAM role definitions, key management procedures - Context: Eliminates secrets exposure vulnerabilities ## Phase 4: Validation and Compliance ### 11. Penetration Testing and Validation - Use Task tool with subagent_type="security-auditor" - Prompt: "Execute comprehensive penetration testing for: $ARGUMENTS. Perform authenticated and unauthenticated testing, API security testing, business logic testing, privilege escalation attempts. Use Burp Suite, Metasploit, and custom exploits. Validate all security controls effectiveness." - Output: Penetration test report, proof-of-concept exploits, remediation validation, security control effectiveness metrics - Context: Validates all implemented security measures ### 12. Compliance and Standards Verification - Use Task tool with subagent_type="security-auditor" - Prompt: "Verify compliance with security frameworks for: $ARGUMENTS. Validate against OWASP ASVS Level 2, CIS Benchmarks, SOC2 Type II requirements, GDPR/CCPA privacy controls, HIPAA/PCI-DSS if applicable. Generate compliance attestation reports." - Output: Compliance assessment report, gap analysis, remediation requirements, audit evidence collection - Context: Ensures regulatory and industry standard compliance ### 13. Security Monitoring and SIEM Integration - Use Task tool with subagent_type="incident-response::devops-troubleshooter" - Prompt: "Implement security monitoring and SIEM for: $ARGUMENTS. Deploy Splunk/ELK/Sentinel integration, configure security event correlation, implement behavioral analytics for anomaly detection, set up automated incident response playbooks, create security dashboards and alerting." - Output: SIEM configuration, correlation rules, incident response playbooks, security dashboards, alert definitions - Context: Establishes continuous security monitoring ## Configuration Options - scanning_depth: "quick" | "standard" | "comprehensive" (default: comprehensive) - compliance_frameworks: ["OWASP", "CIS", "SOC2", "GDPR", "HIPAA", "PCI-DSS"] - remediation_priority: "cvss_score" | "exploitability" | "business_impact" - monitoring_integration: "splunk" | "elastic" | "sentinel" | "custom" - authentication_methods: ["oauth2", "saml", "mfa", "biometric", "passwordless"] ## Success Criteria - All critical vulnerabilities (CVSS 7+) remediated - OWASP Top 10 vulnerabilities addressed - Zero high-risk findings in penetration testing - Compliance frameworks validation passed - Security monitoring detecting and alerting on threats - Incident response time < 15 minutes for critical alerts - SBOM generated and vulnerabilities tracked - All secrets managed through secure vault - Authentication implements MFA and secure session management - Security tests integrated into CI/CD pipeline ## Coordination Notes - Each phase provides detailed findings that inform subsequent phases - Security-auditor agent coordinates with domain-specific agents for fixes - All code changes undergo security review before implementation - Continuous feedback loop between assessment and remediation - Security findings tracked in centralized vulnerability management system - Regular security reviews scheduled post-implementation Security hardening target: $ARGUMENTS --- ## AGI Framework Integration > **Adapted for [@techwavedev/agi-agent-kit](https://www.npmjs.com/package/@techwavedev/agi-agent-kit)** > Original source: [antigravity-awesome-skills](https://github.com/sickn33/antigravity-awesome-skills) ### Memory-First Protocol Cache compliance check results to avoid re-running expensive AWS API calls. Retrieve prior audit findings to track remediation progress across sessions. ```bash # Check for prior security context before starting python3 execution/memory_manager.py auto --query "prior security audit results for Security Scanning Security Hardening" ``` ### Storing Results After completing work, store security decisions for future sessions: ```bash python3 execution/memory_manager.py store \ --content "Audit findings: 3 critical IAM misconfigurations found and remediated" \ --type technical --project \ --tags security-scanning-security-hardening security ``` ### Multi-Agent Collaboration Share security findings with other agents so they avoid introducing vulnerabilities in their code changes. ```bash python3 execution/cross_agent_context.py store \ --agent "" \ --action "Completed security audit — 3 critical findings fixed, compliance score 94%" \ --project ``` ### Signed Audit Trail All security findings are cryptographically signed with the agent's Ed25519 identity, providing tamper-proof audit logs for compliance reporting. ### Semantic Cache for Compliance Cache compliance check results (`semantic_cache.py`) to avoid redundant AWS API calls. Cache hit at similarity >0.92 returns prior results instantly. --- Source attribution: techwavedev Original project: https://github.com/techwavedev/agi-agent-kit/blob/58f5d95434a1adc8b41a4f391d32d95311e54936/templates/skills/extended/security/security-scanning-security-hardening/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright 2024-2026 Elton Machado (TechWaveDev) Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: techwavedev Original project: https://github.com/techwavedev/agi-agent-kit/blob/58f5d95434a1adc8b41a4f391d32d95311e54936/templates/skills/extended/security/security-scanning-security-hardening/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management Roles: Backend Developer, DevOps / SRE, Product Manager, QA / Test Engineer, Security Engineer Specialties: API, Backend, Database, Design, DevOps, Word Documents, Frontend, Git, Mobile, Testing Tools: Gitleaks, Owasp Zap, Semgrep, Snyk, Sonarqube, Trivy, Trufflehog Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 9e3fc6ad29920e31bea756baa287c748d60eaffaa8e1bb14876f70cc167135fa