performing-threat-landscape-assessment-for-sector▌
mukul975/Anthropic-Cybersecurity-Skills · updated May 25, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Conduct a sector-specific threat landscape assessment by analyzing threat actor targeting patterns, common attack vectors, and industry-specific vulnerabilities to inform organizational risk management.
| name | performing-threat-landscape-assessment-for-sector |
| description | Conduct a sector-specific threat landscape assessment by analyzing threat actor targeting patterns, common attack vectors, and industry-specific vulnerabilities to inform organizational risk management. |
| domain | cybersecurity |
| subdomain | threat-intelligence |
| tags | - threat-landscape - sector-analysis - risk-assessment - threat-intelligence - industry-targeting - cti - strategic-intelligence |
| version | '1.0' |
| author | mahipal |
| license | Apache-2.0 |
| d3fend_techniques | - File Metadata Consistency Validation - Application Protocol Command Analysis - Identifier Analysis - Content Format Conversion - Message Analysis |
| nist_csf | - ID.RA-01 - ID.RA-05 - DE.CM-01 - DE.AE-02 |
Performing Threat Landscape Assessment for Sector
Overview
A sector-specific threat landscape assessment analyzes the cyber threat environment facing a particular industry vertical (healthcare, financial services, energy, government, manufacturing) by examining which threat actors target the sector, their preferred attack vectors and TTPs, common vulnerabilities exploited, historical incident data, and emerging threats. This produces actionable intelligence for risk management, security investment prioritization, and board-level reporting.
When to Use
- When conducting security assessments that involve performing threat landscape assessment for sector
- When following incident response procedures for related security events
- When performing scheduled security testing or auditing activities
- When validating security controls through hands-on testing
Prerequisites
- Python 3.9+ with
attackcti,requests,pandas,matplotliblibraries - Access to threat intelligence feeds (AlienVault OTX, MISP, vendor reports)
- MITRE ATT&CK knowledge base for TTP mapping
- Industry-specific ISAC membership (FS-ISAC, H-ISAC, E-ISAC, etc.)
- Understanding of sector-specific regulatory requirements
Key Concepts
Sector Targeting Analysis
Different sectors face different threat profiles. Financial services face sophisticated nation-state actors (Lazarus Group) and cybercriminal groups focused on financial fraud. Healthcare faces ransomware groups exploiting urgency and legacy systems. Energy and critical infrastructure face nation-state groups (TEMP.Veles, Sandworm) with destructive capabilities. Government faces espionage-focused APTs (APT29, APT28, Turla).
Threat Landscape Components
A comprehensive assessment includes: threat actor profiling (groups targeting the sector), attack vector analysis (initial access methods observed), TTP mapping (techniques commonly used against sector), vulnerability landscape (CVEs commonly exploited), incident trend analysis (breach frequency, impact, recovery time), and emerging threats (new groups, evolving techniques, supply chain risks).
Intelligence Sources
Sector-specific intelligence comes from ISACs (Information Sharing and Analysis Centers), government advisories (CISA, FBI, NSA), vendor threat reports (CrowdStrike Annual Threat Report, Mandiant M-Trends, Verizon DBIR), and academic research on sector-specific attacks.
Workflow
Step 1: Identify Threat Actors Targeting the Sector
from attackcti import attack_client
import json
class SectorThreatAssessment:
SECTOR_GROUPS = {
"financial": ["FIN7", "FIN8", "FIN11", "Carbanak", "Lazarus Group",
"Cobalt Group", "TA505", "GOLD SOUTHFIELD"],
"healthcare": ["FIN12", "Ryuk", "Conti", "Wizard Spider",
"GOLD ULRICK", "Vice Society"],
"energy": ["TEMP.Veles", "Sandworm Team", "Dragonfly",
"XENOTIME", "ERYTHRITE", "Berserk Bear"],
"government": ["APT29", "APT28", "Turla", "Gamaredon Group",
"Mustang Panda", "APT41", "Lazarus Group"],
"manufacturing": ["APT41", "TEMP.Veles", "Dragonfly",
"HEXANE", "MAGNALLIUM"],
"technology": ["APT41", "Lazarus Group", "APT10",
"HAFNIUM", "Winnti Group"],
}
def __init__(self, sector):
self.sector = sector.lower()
self.lift = attack_client()
self.groups = self.lift.get_groups()
self.assessment = {
"sector": sector,
"threat_actors": [],
"common_techniques": {},
"attack_vectors": {},
"risk_summary": {},
}
def analyze_sector_actors(self):
"""Analyze threat actors known to target this sector."""
target_groups = self.SECTOR_GROUPS.get(self.sector, [])
actor_profiles = []
for group_name in target_groups:
group = next(
(g for g in self.groups
if g.get("name", "").lower() == group_name.lower()
or group_name.lower() in [a.lower() for a in g.get("aliases", [])]),
None
)
if group:
group_id = ""
for ref in group.get("external_references", []):
if ref.get("source_name") == "mitre-attack":
group_id = ref.get("external_id", "")
break
techniques = []
if group_id:
techs = self.lift.get_techniques_used_by_group(group_id)
for t in techs:
for ref in t.get("external_references", []):
if ref.get("source_name") == "mitre-attack":
techniques.append({
"id": ref.get("external_id", ""),
"name": t.get("name", ""),
})
break
profile = {
"name": group.get("name", ""),
"aliases": group.get("aliases", []),
"description": group.get("description", "")[:300],
"attack_id": group_id,
"technique_count": len(techniques),
"techniques": techniques[:20],
}
actor_profiles.append(profile)
print(f" [+] {group.get('name')}: {len(techniques)} techniques")
self.assessment["threat_actors"] = actor_profiles
print(f"[+] Profiled {len(actor_profiles)} threat actors for {self.sector}")
return actor_profiles
def identify_common_techniques(self):
"""Find the most commonly used techniques across sector actors."""
from collections import Counter
technique_counter = Counter()
for actor in self.assessment["threat_actors"]:
for tech in actor.get("techniques", []):
technique_counter[f"{tech['id']}:{tech['name']}"] += 1
common = technique_counter.most_common(20)
self.assessment["common_techniques"] = [
{
"technique": tech.split(":")[0],
"name": tech.split(":")[1] if ":" in tech else "",
"actor_count": count,
"actors_using": [
a["name"] for a in self.assessment["threat_actors"]
if any(t["id"] == tech.split(":")[0] for t in a.get("techniques", []))
],
}
for tech, count in common
]
print(f"\n=== Top Techniques for {self.sector.upper()} ===")
for entry in self.assessment["common_techniques"][:10]:
print(f" {entry['technique']} {entry['name']}: "
f"used by {entry['actor_count']} groups")
return self.assessment["common_techniques"]
assessment = SectorThreatAssessment("financial")
assessment.analyze_sector_actors()
assessment.identify_common_techniques()
Step 2: Analyze Attack Vectors and Initial Access
def analyze_attack_vectors(assessment):
"""Analyze initial access vectors common for the sector."""
initial_access_techniques = [
t for t in assessment.assessment["common_techniques"]
if t["technique"].startswith("T1566") or t["technique"].startswith("T1190")
or t["technique"].startswith("T1133") or t["technique"].startswith("T1078")
or t["technique"].startswith("T1195")
]
# Supplement with known sector-specific vectors
sector_vectors = {
"financial": {
"primary": ["Spearphishing (T1566)", "Exploit Public-Facing App (T1190)",
"Valid Accounts (T1078)", "Supply Chain Compromise (T1195)"],
"emerging": ["MFA Fatigue/Push Bombing", "QR Code Phishing (Quishing)",
"Business Email Compromise", "API Key Theft"],
},
"healthcare": {
"primary": ["Spearphishing (T1566)", "Exploit Public-Facing App (T1190)",
"External Remote Services (T1133)", "Valid Accounts (T1078)"],
"emerging": ["IoMT Device Exploitation", "Telehealth Platform Attacks",
"Medical Device Firmware Attacks", "Supply Chain via EHR Vendors"],
},
"energy": {
"primary": ["Spearphishing (T1566)", "Exploit Public-Facing App (T1190)",
"External Remote Services (T1133)", "Supply Chain Compromise (T1195)"],
"emerging": ["OT/ICS Protocol Exploitation", "Remote Access to SCADA",
"Engineering Workstation Compromise", "Vendor VPN Exploitation"],
},
}
vectors = sector_vectors.get(assessment.sector, {})
assessment.assessment["attack_vectors"] = vectors
return vectors
Step 3: Generate Sector Threat Report
def generate_sector_report(assessment):
data = assessment.assessment
report = f"""# {data['sector'].title()} Sector Threat Landscape Assessment
Generated: {datetime.datetime.now().isoformat()}
## Executive Summary
This assessment analyzes the cyber threat landscape for the {data['sector']} sector,
identifying {len(data['threat_actors'])} active threat groups, their preferred techniques,
and recommended defensive priorities.
## Threat Actor Summary
| Actor | ATT&CK ID | Techniques | Key Focus |
|-------|-----------|------------|-----------|
"""
for actor in data["threat_actors"]:
report += (f"| {actor['name']} | {actor['attack_id']} "
f"| {actor['technique_count']} | {actor['description'][:60]}... |\n")
report += f"""
## Most Common Techniques
| Rank | Technique | Name | Groups Using |
|------|-----------|------|-------------|
"""
for i, tech in enumerate(data.get("common_techniques", [])[:15], 1):
actors = ", ".join(tech["actors_using"][:3])
report += f"| {i} | {tech['technique']} | {tech['name']} | {actors} |\n"
vectors = data.get("attack_vectors", {})
report += f"""
## Attack Vectors
### Primary Vectors
"""
for v in vectors.get("primary", []):
report += f"- {v}\n"
report += "\n### Emerging Vectors\n"
for v in vectors.get("emerging", []):
report += f"- {v}\n"
report += """
## Recommendations
1. Prioritize detections for the top 10 techniques used by sector-targeting groups
2. Conduct threat-informed red team exercises mimicking identified actors
3. Join sector ISAC for real-time threat sharing
4. Implement controls for identified initial access vectors
5. Review supply chain security posture for sector-specific risks
"""
with open(f"threat_landscape_{data['sector']}.md", "w") as f:
f.write(report)
print(f"[+] Sector report saved: threat_landscape_{data['sector']}.md")
generate_sector_report(assessment)
Validation Criteria
- Sector-specific threat actors identified and profiled
- Common techniques across actors analyzed and ranked
- Attack vectors mapped for the target sector
- Emerging threats identified based on recent intelligence
- Comprehensive sector threat report generated
- Recommendations actionable for security investment decisions
References
How to use performing-threat-landscape-assessment-for-sector on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add performing-threat-landscape-assessment-for-sector
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches performing-threat-landscape-assessment-for-sector from GitHub repository mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate performing-threat-landscape-assessment-for-sector. Access the skill through slash commands (e.g., /performing-threat-landscape-assessment-for-sector) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★28 reviews- ★★★★★Dhruvi Jain· Dec 28, 2024
performing-threat-landscape-assessment-for-sector has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Zaid Nasser· Dec 24, 2024
performing-threat-landscape-assessment-for-sector reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Benjamin Thompson· Dec 8, 2024
We added performing-threat-landscape-assessment-for-sector from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kabir Flores· Nov 27, 2024
Keeps context tight: performing-threat-landscape-assessment-for-sector is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Oshnikdeep· Nov 19, 2024
Solid pick for teams standardizing on skills: performing-threat-landscape-assessment-for-sector is focused, and the summary matches what you get after install.
- ★★★★★Isabella Choi· Nov 15, 2024
Registry listing for performing-threat-landscape-assessment-for-sector matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kabir Kim· Nov 7, 2024
performing-threat-landscape-assessment-for-sector is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★William Mehta· Oct 26, 2024
Useful defaults in performing-threat-landscape-assessment-for-sector — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Noor Srinivasan· Oct 18, 2024
performing-threat-landscape-assessment-for-sector has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ganesh Mohane· Oct 10, 2024
We added performing-threat-landscape-assessment-for-sector from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 28