All categories
DevOps & Cloud
Deployment, cloud, containers, CI/CD, monitoring, and infrastructure
- 19,628
- 818
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse devops & cloud skills
Showing 14,161–14,184 of 19,628 skills
- Configuring Suricata For Network Monitoring'Deploys and configures Suricata IDS/IPS with Emerging Threats rulesets,Votes: 0GitHub stars: 67
- Configuring Snort Ids For Intrusion Detection'Installs, configures, and tunes Snort 3 to monitor network trafficVotes: 0GitHub stars: 67
- Configuring Pfsense Firewall Rules'Configures pfSense firewall rules, NAT policies, IPsec/OpenVPN tunnels,Votes: 0GitHub stars: 67
- Configuring Microsegmentation For Zero TrustConfigures microsegmentation policies to enforce least-privilege workload-to-workloadVotes: 0GitHub stars: 67
- Configuring Host Based Intrusion Detection'Configures host-based intrusion detection systems (HIDS) to monitorVotes: 0GitHub stars: 67
- Configuring Aws Verified Access For ZtnaConfigure AWS Verified Access to provide VPN-less zero trust networkVotes: 0GitHub stars: 67
- Conducting Spearphishing Simulation CampaignRun a targeted spearphishing simulation for initial access by developing OSINT-derived pretexts, building payloads (HTML smuggling, macro docs, ISO/LNK, OneNote, QR codes), standing up look-alike-domain email infrastructure with SPF/DKIM/DMARC via GoPhish, and tracking results. Use in authorized engagements to gain initial access via personalized phishing against specific individuals, distinct from broad campaigns.Votes: 0GitHub stars: 67
- Conducting Post Incident Lessons LearnedFacilitate structured post-incident reviews to identify root causes,Votes: 0GitHub stars: 67
- Conducting Malware Incident ResponseRespond to malware infections across enterprise endpoints by identifying the malware family, determining infection vectors, assessing spread, and executing containment, analysis, eradication, and recovery procedures aligned to MITRE ATT&CK. Use when responding to a confirmed or suspected malware infection, including trojan/worm/ransomware outbreaks, malware triage, or infected endpoint remediation.Votes: 0GitHub stars: 67
- Conducting Cloud Incident ResponseRespond to security incidents in AWS, Azure, and GCP via identity-based containment, cloud-native log analysis (CloudTrail, Azure Activity Logs, GCP Audit Logs), resource isolation, and forensic evidence acquisition adapted for ephemeral cloud infrastructure. Use when CSPM alerts or audit logs show compromised cloud credentials, unauthorized IAM changes, or a breach spanning cloud services.Votes: 0GitHub stars: 67
- Collecting Indicators Of Compromise'Systematically collects, categorizes, and distributes indicators ofVotes: 0GitHub stars: 67
- Building Threat Intelligence PlatformDesign and deploy a Threat Intelligence Platform (TIP) by integrating open-source CTI tools (MISP, OpenCTI, TheHive, Cortex) into a unified system with feed ingestion pipelines, enrichment workflows, STIX/TAXII interoperability, and analyst dashboards. Use when architecting or standing up a centralized CTI platform to collect, analyze, and disseminate threat intelligence across a security team.Votes: 0GitHub stars: 67
- Building Threat Intelligence Enrichment In SplunkBuild automated IOC enrichment pipelines in Splunk Enterprise Security by ingesting threat feeds into KV Store collections and correlating them against security events via lookup tables, modular inputs, and the Threat Intelligence Framework. Use when wiring threat intel into Splunk correlation searches to flag IOC matches and cut SOC triage time.Votes: 0GitHub stars: 67
- Building Threat Feed Aggregation With MispDeploy MISP via Docker and configure feeds from sources like abuse.ch, AlienVault OTX, and CIRCL to aggregate, correlate, and distribute threat intelligence, including automated feed synchronization and STIX/TAXII-based integration with Splunk, Elasticsearch, and SOAR platforms. Use when standing up centralized IOC management or wiring multi-source threat feeds into a SIEM.Votes: 0GitHub stars: 67
- Building Threat Actor Profile From OsintBuild threat actor profiles by collecting OSINT from vendor reports, paste sites, dark web forums, social media, and code repos, correlating indicators, mapping adversary infrastructure with tools like Maltego and SpiderFoot, and producing structured dossiers of motivations, capabilities, infrastructure, and TTPs. Use when performing attribution or building an adversary dossier from open-source intelligence.Votes: 0GitHub stars: 67
- Openspec ExploreEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.Votes: 0GitHub stars: 840
- Openspec Verify ChangeVerify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.Votes: 0GitHub stars: 840
- Openspec Sync SpecsSync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.Votes: 0GitHub stars: 840
- Openspec OnboardGuided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.Votes: 0GitHub stars: 840
- Openspec New ChangeStart a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.Votes: 0GitHub stars: 840
- Openspec Ff ChangeFast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.Votes: 0GitHub stars: 840
- Openspec Continue ChangeContinue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.Votes: 0GitHub stars: 840
- Openspec Bulk Archive ChangeArchive multiple completed changes at once. Use when archiving several parallel changes.Votes: 0GitHub stars: 840
- Openspec Archive ChangeArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.Votes: 0GitHub stars: 840