Skip to content
cccskills
FreePublished on GitHub

horizon-scanning

Use when the user asks "what is coming next?", wants strategic forecasting, or is hunting weak signals of emerging threats before they materialise. Covers signal identification, trend analysis, and scenario development.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Horizon Scanning

Horizon scanning identifies emerging threats, opportunities, and developments that could impact the organisation's security posture in the medium to long term (6-24 months).

Process

1. Define Scope

  • Time horizon (6 months? 12 months? 24 months?)
  • Focus areas (specific sectors, threat types, geographies)
  • Stakeholder needs (what decisions will this inform?)

2. Identify Weak Signals

Weak signals are early indicators of emerging trends. Sources:

  • Academic research and conference papers (BlackHat, DEF CON, CCC, academic journals)
  • Underground forum discussions (new tools, techniques being discussed)
  • Patent filings and startup activity (indicators of new capabilities)
  • Geopolitical developments (sanctions, conflicts, elections)
  • Regulatory changes (new compliance requirements creating new attack surfaces)
  • Technology adoption trends (new tech = new attack surface)

3. Categorise Signals

CategoryExamples
Emerging TTPsNew exploitation techniques, novel social engineering methods, AI-augmented attacks
Technology shiftsNew platforms widely adopted, legacy tech being deprecated, cloud migration patterns
Threat actor evolutionNew groups emerging, existing groups changing targets, capability development
Geopolitical driversConflicts, sanctions, elections, diplomatic shifts
Regulatory/legalNew laws, enforcement actions, liability changes
Underground economyNew services, market shifts, ecosystem changes

4. Develop Scenarios

For each significant signal, develop three scenarios:

  • Best case: Signal does not materialise or is mitigated
  • Worst case: Signal materialises with maximum impact
  • Most likely: Balanced assessment based on available evidence

5. Assess Impact and Likelihood

For each scenario:

  • Likelihood (using probability yardstick from likelihood-language skill)
  • Impact on organisation (Critical/High/Moderate/Low/Negligible)
  • Time to materialise
  • Confidence in assessment

6. Identify Early Warning Indicators

For each high-impact scenario, define:

  • What observable indicators would suggest this is materialising?
  • Where would we see these indicators? (collection sources)
  • How frequently should we monitor?

Output Template

## Horizon Scanning Report: [Focus Area]
**Period**: [Time horizon]
**Date**: YYYY-MM-DD

### Executive Summary
[Key emerging threats and their implications]

### Emerging Threats

#### [Threat 1]: [Title]
- **Signal strength**: Weak / Emerging / Established
- **Time horizon**: [When could this materialise?]
- **Likelihood**: [Probability yardstick term]
- **Potential impact**: [Critical/High/Moderate/Low]
- **Confidence**: [Level with rationale]
- **Description**: [What is this threat and why does it matter?]
- **Early warning indicators**: [What to watch for]
- **Recommended action**: [Proactive steps]

### Scenario Analysis
[For top 2-3 threats, develop best/worst/most likely scenarios]

### Collection Gaps
[What we need to monitor but currently can't]

Common Signals to Monitor (CTI)

  • AI-powered phishing/deepfakes maturation
  • Quantum computing impact on cryptography
  • Supply chain security tooling gaps
  • Cloud-native attack technique evolution
  • Ransomware business model evolution
  • Nation-state cyber capability proliferation
  • Infostealer-to-ransomware pipeline evolution
  • Edge device/IoT exploitation trends

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

AbuseIPDB API reference. IP reputation and abuse report lookups.

The English summary is being prepared. Showing the original description.

Liberty91LTD/cti-skills27Updated Sep 30, 2026

ach

Free

Analysis of Competing Hypotheses — structured technique for evaluating multiple explanations against evidence. Use when facing ambiguous attribution or multiple plausible scenarios. Prefers graded evidence items from /quality-of-information-check and runs that skill first when handed raw URLs or text. Runs on ungraded evidence when asked, labelled as such, unweighted, and capped at Moderate confidence.

The English summary is being prepared. Showing the original description.

Liberty91LTD/cti-skills27Updated Sep 30, 2026

Use when documenting a named campaign across time and victims, the user asks to start or update a campaign record, or another skill identified a multi-incident cluster that warrants formal tracking. Provides the template (timeline, attribution, victimology, attack chain, Diamond Model mapping, IOC clusters) and the lifecycle from active to historical.

The English summary is being prepared. Showing the original description.

Liberty91LTD/cti-skills27Updated Sep 30, 2026

Use when the user asks about carding, BIN attacks, payment-card breach markets, fullz/CVV2 trade, autoshops (BidenCash, Brian's Club, Russianmarket, B1ack's Stash), or financial-fraud TTPs. Self-updating knowledge cell.

The English summary is being prepared. Showing the original description.

Liberty91LTD/cti-skills27Updated Sep 30, 2026

Censys API v2 reference. Host reconnaissance and certificate data.

The English summary is being prepared. Showing the original description.

Liberty91LTD/cti-skills27Updated Sep 30, 2026

Use when the user asks about Chinese state-sponsored cyber operations or specific PRC-aligned actors (APT41, Volt Typhoon, Mustang Panda, APT10, APT31, Salt Typhoon, etc.), MSS/PLA-attributed campaigns, or PRC sector targeting. Self-updating knowledge cell.

The English summary is being prepared. Showing the original description.

Liberty91LTD/cti-skills27Updated Sep 30, 2026

See all skills by Liberty91LTD

Report a problem with this skill