All authors
Claude Skills by CyberStrikeus
github.com/CyberStrikeus7,689 skills3 installs18,525 views
- Cis Nginx V300 4 1 1Ensure HTTP is redirected to HTTPS (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 4 1 10Ensure the upstream traffic server certificate is trusted (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 4 1 11Ensure Secure Session Resumption is Enabled (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 4 1 12Ensure HTTP/3.0 is used (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 4 1 2Ensure a trusted certificate and trust chain is installed (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 4 1 3Ensure private key permissions are restricted (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 4 1 4Ensure only modern TLS protocols are used (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 4 1 5Disable weak ciphers (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 4 1 6Ensure awareness of TLS 1.3 new Diffie-Hellman parameters (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 4 1 7Ensure Online Certificate Status Protocol (OCSP) stapling is enabled (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 4 1 8Ensure HTTP Strict Transport Security (HSTS) is enabled (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 4 1 9Ensure upstream server traffic is authenticated with a client certificate (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 5 1 1Ensure allow and deny filters limit access to specific IP addresses (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 5 1 2Ensure only approved HTTP methods are allowed (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 5 2 1Ensure timeout values for reading the client header and body are set correctly (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 5 2 2Ensure the maximum request body size is set correctly (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 5 2 3Ensure the maximum buffer size for URIs is defined (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 5 2 4Ensure the number of connections per IP address is limited (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 5 2 5Ensure rate limits by IP address are set (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 5 3 1Ensure X-Content-Type-Options header is configured and enabled (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 5 3 2Ensure that Content Security Policy (CSP) is enabled and configured properly (Manual)Votes: 0GitHub stars: 2,182
- Cis Nginx V300 5 3 3Ensure the Referrer Policy is enabled and configured properly (Manual)Votes: 0GitHub stars: 2,182
- Adverse Event Analysis (DE.AE) Adverse Event AnalysisAnomalies, indicators of compromise, and other potentially adverse events are analyzed to characterize the events and detect cybersecurity incidentsVotes: 0GitHub stars: 2,182
- Continuous Monitoring (DE.CM) Continuous MonitoringAssets are monitored to find anomalies, indicators of compromise, and other potentially adverse eventsVotes: 0GitHub stars: 2,182
- DE.AE 01 Deae 01A baseline of network operations and expected data flows for users and systems is established and managedVotes: 0GitHub stars: 2,182
- DE.AE 02 Deae 02Potentially adverse events are analyzed to better understand associated activitiesVotes: 0GitHub stars: 2,182
- DE.AE 03 Deae 03Information is correlated from multiple sourcesVotes: 0GitHub stars: 2,182
- DE.AE 04 Deae 04The estimated impact and scope of adverse events are understoodVotes: 0GitHub stars: 2,182
- DE.AE 05 Deae 05Incident alert thresholds are establishedVotes: 0GitHub stars: 2,182
- DE.AE 06 Deae 06Information on adverse events is provided to authorized staff and toolsVotes: 0GitHub stars: 2,182
- DE.AE 07 Deae 07Cyber threat intelligence and other contextual information are integrated into the analysisVotes: 0GitHub stars: 2,182
- DE.AE 08 Deae 08Incidents are declared when adverse events meet the defined incident criteriaVotes: 0GitHub stars: 2,182
- DE.CM 01 Decm 01Networks and network services are monitored to find potentially adverse eventsVotes: 0GitHub stars: 2,182
- DE.CM 02 Decm 02The physical environment is monitored to find potentially adverse eventsVotes: 0GitHub stars: 2,182
- DE.CM 03 Decm 03Personnel activity and technology usage are monitored to find potentially adverse eventsVotes: 0GitHub stars: 2,182
- DE.CM 04 Decm 04Malicious code is detectedVotes: 0GitHub stars: 2,182
- DE.CM 05 Decm 05Unauthorized mobile code is detectedVotes: 0GitHub stars: 2,182
- DE.CM 06 Decm 06External service provider activities and services are monitored to find potentially adverse eventsVotes: 0GitHub stars: 2,182
- DE.CM 07 Decm 07Monitoring for unauthorized personnel, connections, devices, and software is performedVotes: 0GitHub stars: 2,182
- DE.CM 08 Decm 08Vulnerability scans are performedVotes: 0GitHub stars: 2,182
- DE.CM 09 Decm 09Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse eventsVotes: 0GitHub stars: 2,182
- DE.DP 01 Dedp 01Roles and responsibilities for detection are well defined to ensure accountabilityVotes: 0GitHub stars: 2,182
- DE.DP 02 Dedp 02Detection activities comply with all applicable requirementsVotes: 0GitHub stars: 2,182
- DE.DP 03 Dedp 03Detection processes are testedVotes: 0GitHub stars: 2,182
- DE.DP 04 Dedp 04Event detection information is communicatedVotes: 0GitHub stars: 2,182
- DE.DP 05 Dedp 05Detection processes are continuously improvedVotes: 0GitHub stars: 2,182
- Detection Processes (DE.DP) Detection ProcessesDetection ProcessesVotes: 0GitHub stars: 2,182
- Cybersecurity Supply Chain Risk Management (GV.SC) Cybersecurity Supply Chain Risk ManagementCyber supply chain risk management processes are identified, established, managed, monitored, and improved by organizational stakeholdersVotes: 0GitHub stars: 2,182
- GV.OC 01 Gvoc 01The organizational mission is understood and informs cybersecurity risk managementVotes: 0GitHub stars: 2,182
- GV.OC 02 Gvoc 02Internal and external stakeholders are understood, and their needs and expectations regarding cybersecurity risk management are understood and consideVotes: 0GitHub stars: 2,182