[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFQJMKC6TBNWJ5HXZFC1ME":3,"skill-same:01M6AFQJMKC6TBNWJ5HXZFC1ME":129},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":73,"repositoryHtmlUrl":74,"repositoryHomepageUrl":75,"ownerHtmlUrl":76,"ownerBlogUrl":77,"ownerDescription":78,"updatedAt":79,"install":80,"resources":93},"01M6AFQJMKC6TBNWJ5HXZFC1ME","performing-cryptographic-audit-of-application",null,"A cryptographic audit systematically reviews an application's use of cryptographic primitives, protocols, and key management to identify vulnerabilities such as weak algorithms, insecure modes, hardco","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35990,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-cryptographic-audit-of-application\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"audit","performing cryptographic audit of application","review","security","cybersecurity","vulnerabilities","pr","assessment","protocols","compliance","reconnaissance","cryptography","initial-access","vulnerability-assessment","credentials","security-review","2026-11-10 10:12:30",false,"---\nname: performing-cryptographic-audit-of-application\ndescription: A cryptographic audit systematically reviews an application's use of\n  cryptographic primitives, protocols, and key management to identify vulnerabilities\n  such as weak algorithms, insecure modes, hardco\ndomain: cybersecurity\nsubdomain: cryptography\ntags:\n- cryptography\n- audit\n- security-review\n- compliance\n- vulnerability-assessment\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.DS-01\n- PR.DS-02\n- PR.DS-10\nmitre_attack:\n- T1600\n- T1573\n- T1553\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - reconnaissance\n  - initial-access\n  - positioning\n  techniques:\n  - id: T1557\n    name: Adversary-in-the-Middle\n    tactic: positioning\n    source: attack\n  - id: T1555\n    name: Credentials from Password Stores\n    tactic: reconnaissance\n    source: attack\n  - id: F1006.001\n    name: 'Account Takeover: Exposed API Key'\n    tactic: initial-access\n    source: f3\n  - id: F1004\n    name: Access with Stolen Session Cookie\n    tactic: initial-access\n    source: f3\n---\n# Performing Cryptographic Audit of Application\n\n## Overview\n\nA cryptographic audit systematically reviews an application's use of cryptographic primitives, protocols, and key management to identify vulnerabilities such as weak algorithms, insecure modes, hardcoded keys, insufficient entropy, and protocol misconfigurations. This skill covers building an automated crypto audit tool that scans Python and configuration files for common cryptographic weaknesses.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing cryptographic audit of application\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with cryptography concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Detect usage of deprecated algorithms (MD5, SHA-1, DES, RC4)\n- Identify insecure cipher modes (ECB) and padding schemes\n- Find hardcoded keys, passwords, and secrets in source code\n- Verify TLS\u002FSSL configuration strength\n- Check key derivation function parameters\n- Validate random number generator usage\n- Produce a structured audit report with findings and remediation\n\n## Key Concepts\n\n### Cryptographic Weakness Categories\n\n| Category | Examples | Risk Level |\n|----------|----------|------------|\n| Weak Hashing | MD5, SHA-1 for integrity\u002Fsignatures | High |\n| Insecure Encryption | DES, 3DES, RC4, Blowfish | High |\n| Bad Cipher Mode | ECB mode for any block cipher | High |\n| Insufficient Key Size | RSA \u003C 2048, AES-128 for long-term | Medium |\n| Hardcoded Secrets | Keys\u002Fpasswords in source code | Critical |\n| Weak KDF | Low iteration PBKDF2, plain MD5 | High |\n| Poor Entropy | time-based seeds, predictable IVs | High |\n| Deprecated Protocols | SSLv3, TLS 1.0, TLS 1.1 | High |\n\n## Security Considerations\n\n- Review both application code and configuration files\n- Check third-party dependencies for known crypto vulnerabilities\n- Verify certificates and TLS configurations on deployed servers\n- Ensure secrets are loaded from environment variables or vaults\n- Review key storage and rotation practices\n\n## Validation Criteria\n\n- [ ] Scanner detects all injected test weaknesses\n- [ ] MD5\u002FSHA-1 usage for security purposes is flagged\n- [ ] ECB mode usage is flagged\n- [ ] Hardcoded keys\u002Fpasswords are detected\n- [ ] Weak KDF parameters are identified\n- [ ] Report includes severity, location, and remediation\n- [ ] False positive rate is below 10%\n","# Performing Cryptographic Audit of Application\n\n## Overview\n\nA cryptographic audit systematically reviews an application's use of cryptographic primitives, protocols, and key management to identify vulnerabilities such as weak algorithms, insecure modes, hardcoded keys, insufficient entropy, and protocol misconfigurations. This skill covers building an automated crypto audit tool that scans Python and configuration files for common cryptographic weaknesses.\n\n\n## When to Use\n\n- When conducting security assessments that involve performing cryptographic audit of application\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with cryptography concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Detect usage of deprecated algorithms (MD5, SHA-1, DES, RC4)\n- Identify insecure cipher modes (ECB) and padding schemes\n- Find hardcoded keys, passwords, and secrets in source code\n- Verify TLS\u002FSSL configuration strength\n- Check key derivation function parameters\n- Validate random number generator usage\n- Produce a structured audit report with findings and remediation\n\n## Key Concepts\n\n### Cryptographic Weakness Categories\n\n| Category | Examples | Risk Level |\n|----------|----------|------------|\n| Weak Hashing | MD5, SHA-1 for integrity\u002Fsignatures | High |\n| Insecure Encryption | DES, 3DES, RC4, Blowfish | High |\n| Bad Cipher Mode | ECB mode for any block cipher | High |\n| Insufficient Key Size | RSA \u003C 2048, AES-128 for long-term | Medium |\n| Hardcoded Secrets | Keys\u002Fpasswords in source code | Critical |\n| Weak KDF | Low iteration PBKDF2, plain MD5 | High |\n| Poor Entropy | time-based seeds, predictable IVs | High |\n| Deprecated Protocols | SSLv3, TLS 1.0, TLS 1.1 | High |\n\n## Security Considerations\n\n- Review both application code and configuration files\n- Check third-party dependencies for known crypto vulnerabilities\n- Verify certificates and TLS configurations on deployed servers\n- Ensure secrets are loaded from environment variables or vaults\n- Review key storage and rotation practices\n\n## Validation Criteria\n\n- [ ] Scanner detects all injected test weaknesses\n- [ ] MD5\u002FSHA-1 usage for security purposes is flagged\n- [ ] ECB mode usage is flagged\n- [ ] Hardcoded keys\u002Fpasswords are detected\n- [ ] Weak KDF parameters are identified\n- [ ] Report includes severity, location, and remediation\n- [ ] False positive rate is below 10%\n",{"name":5,"tags":40,"author":41,"domain":23,"license":15,"version":42,"mitre_f3":43,"nist_csf":62,"subdomain":30,"description":7,"mitre_attack":66},[30,19,34,28,32],"mahipal","1.0",{"tactics":44,"version":46,"techniques":47},[29,31,45],"positioning","1.1",[48,52,55,59],{"id":49,"name":50,"source":51,"tactic":45},"T1557","Adversary-in-the-Middle","attack",{"id":53,"name":54,"source":51,"tactic":29},"T1555","Credentials from Password Stores",{"id":56,"name":57,"source":58,"tactic":31},"F1006.001","Account Takeover: Exposed API Key","f3",{"id":60,"name":61,"source":58,"tactic":31},"F1004","Access with Stolen Session Cookie",[63,64,65],"PR.DS-01","PR.DS-02","PR.DS-10",[67,68,69],"T1600","T1573","T1553","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fperforming-cryptographic-audit-of-application",4395,"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":81,"prompt":91,"zipAvailable":92},[82,85,88],{"tool":83,"command":84},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-cryptographic-audit-of-application",{"tool":86,"command":87},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-cryptographic-audit-of-application",{"tool":89,"command":90},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-cryptographic-audit-of-application","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-cryptographic-audit-of-application\u002FSKILL.md",true,[94,100,105,111,115,119,125],{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"assets\u002Ftemplate.md","ASSET","资产文件",1802,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-cryptographic-audit-of-application\u002Fassets\u002Ftemplate.md",{"path":101,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-cryptographic-audit-of-application\u002FLICENSE",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fapi-reference.md","REFERENCE","参考文档",6733,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-cryptographic-audit-of-application\u002Freferences\u002Fapi-reference.md",{"path":112,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fstandards.md",1477,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-cryptographic-audit-of-application\u002Freferences\u002Fstandards.md",{"path":116,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fworkflows.md",1443,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-cryptographic-audit-of-application\u002Freferences\u002Fworkflows.md",{"path":120,"resourceType":121,"resourceTypeDesc":122,"sizeBytes":123,"sourceHtmlUrl":124},"scripts\u002Fagent.py","SCRIPT","脚本",13103,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-cryptographic-audit-of-application\u002Fscripts\u002Fagent.py",{"path":126,"resourceType":121,"resourceTypeDesc":122,"sizeBytes":127,"sourceHtmlUrl":128},"scripts\u002Fprocess.py",13328,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-cryptographic-audit-of-application\u002Fscripts\u002Fprocess.py",[130,159,183,210,236,262],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":141,"publishedAt":35},"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",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[142,143,144,145,22,23,146,147,25,148,149,150,151,152,153,154,155,156,157,158],"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":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":166,"publishedAt":35},"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",[165],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},[167,155,168,169,22,170,23,25,171,172,173,174,175,176,177,178,179,180,181,182],"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":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":193,"publishedAt":35},"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",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},[177,194,195,196,197,23,198,199,171,28,200,201,202,203,204,205,206,207,208,209],"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":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":35},"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",[216],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},[218,219,220,23,221,222,223,224,225,226,227,228,229,230,231,232,174,233,234,235],"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":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":243,"publishedAt":35},"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",[242],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},[24,244,245,23,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261],"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":263,"name":264,"nameZh":6,"description":265,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":266,"categories":267,"keywords":269,"publishedAt":35},"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",[268],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},[22,270,23,271,272,273,274,275,276,277,278,205,279,206,280,281,282,283,284,285],"triaging security incident","siem","file","ioc","soc","NIST-800-61","NIST","severity","edr","execution","analysis","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]