Security Methodology

How I Approach
Security Risk

An 8-stage framework for identifying and eliminating risk.

Risk assessment isn't a checkbox — it's the foundation of every security decision I make. This page documents my personal framework for identifying, analyzing, and mitigating cyber risk across enterprise environments. Aligned with ISO 27001, NIST, and COSO standards.

ISO 27001 ALIGNED
NIST CSF 2.0
COSO ERM
8-STAGE PROCESS
IDENTIFY
Assets, threats & vulnerabilities
ANALYZE
Likelihood & business impact
TREAT
Remediate, mitigate or transfer
MONITOR
Continuously review & improve
Process Stages · 01 through 08
01
Discovery Phase
Identify Assets & Data

Inventory every piece of hardware, software, network segment, and data repository that requires protection. You cannot defend what you don't know exists — a complete asset register is the bedrock of every subsequent step.

You can't
defend what
you don't
know exists.
⚙ Tools I Use
DISCLANSurveyor
RMMConnectWise Automate
EDRSentinelOne
MDRHuntress
IAMActive Directory
CLOUDAzure / M365
✓ Checklist
✓
Complete hardware inventory (servers, endpoints, IoT)
✓
Map all software and SaaS licenses in use
✓
Classify data by sensitivity (PII, PCI, IP)
✓
Identify shadow IT and unmanaged devices
✓
Document network topology and data flows
✓
Assign asset owner and business unit to each
02
Threat Intelligence Phase
Identify Threats

Map the threat landscape specific to your environment — malware, phishing, ransomware, insider threats, and supply chain compromise. Generic threat lists aren't enough; threat identification must be grounded in your industry, geography, and asset profile.

Generic threat
lists aren't
enough — know
your landscape.
⚙ Tools I Use
EDRSentinelOne
MDRHuntress
DNSCisco Umbrella
SIEMGraylog
TIMITRE ATT&CK
CLOUDAzure Security
✓ Checklist
✓
Review MITRE ATT&CK for relevant TTPs
✓
Subscribe to industry-specific threat feeds
✓
Document external threat actors and motivations
✓
Assess insider threat risk (access levels, behaviour)
✓
Review supply chain and third-party risks
✓
Map threats to specific assets from Step 1
03
Vulnerability Analysis Phase
Identify Vulnerabilities

Surface weaknesses across configurations, access controls, software versions, and human factors. Vulnerabilities aren't just CVEs — they include misconfigured firewall rules, excessive permissions, and a workforce that hasn't been phishing-tested in 12 months.

Vulns aren't
just CVEs —
people and
process matter.
⚙ Tools I Use
EDRSentinelOne
MDRHuntress
RMMConnectWise Automate
PATCHWSUS
IAMActive Directory / GPO
CLOUDAzure Security Audits
✓ Checklist
✓
Run authenticated vulnerability scans on all assets
✓
Audit firewall, ACL, and group policy configurations
✓
Review privileged account access and MFA coverage
✓
Test patch compliance baselines (target: 93%+)
✓
Conduct phishing simulation assessment
✓
Validate backup integrity and recovery procedures
04
Probability Estimation Phase
Analyze Likelihood

Evaluate the realistic probability of each threat-vulnerability pair being exploited, factoring in threat actor capabilities, attack frequency data, and current defensive measures. Likelihood is not intuition — it must be scored against repeatable criteria.

Likelihood
is scored,
not assumed
or guessed.
⚙ Tools I Use
SIEMGraylog
EDRSentinelOne
MDRHuntress
TIMITRE ATT&CK
RMMConnectWise Automate
DBNVD / NIST CVE DB
✓ Checklist
✓
Score each risk using 1–5 likelihood scale
✓
Reference CVSS scores for technical vulnerabilities
✓
Cross-reference real-world exploit activity (CISA KEV)
✓
Account for current controls reducing exposure
✓
Validate scores with threat intel data
✓
Document rationale for each likelihood rating
05
Business Impact Phase
Analyze Impact

Estimate the potential damage across four dimensions: financial loss, operational downtime, data theft and regulatory exposure, and long-term reputational damage. Impact scoring without financial context fails to drive executive buy-in or appropriate budget allocation.

Impact without
financial context
won't move
decision-makers.
⚙ Tools I Use
PSAConnectWise Manage
CLOUDAzure Security Audits
BDRDatto
BDRVeeam
REGGDPR / HIPAA Matrix
✓ Checklist
✓
Estimate direct financial costs (recovery, fines)
✓
Calculate operational downtime cost per hour
✓
Assess regulatory exposure (GDPR, HIPAA, SOC 2)
✓
Quantify reputational and customer-loss risk
✓
Score each asset's impact on 1–5 scale
✓
Present worst-case / likely-case scenarios
06
Risk Calculation Phase
Evaluate Risk Level

Combine likelihood and impact scores into a single risk rating. This produces a prioritized, defensible register that drives resource allocation. Not all risks are equal — the matrix forces honest prioritization over gut feelings.

Core Risk Formula
RISK = LIKELIHOOD × IMPACT

Scored on a 5×5 matrix — values from 1 (minimal) to 25 (critical). Anything ≥ 15 requires immediate treatment.

LIKELIHOOD ↓ / IMPACT → 1 — Minimal 2 — Minor 3 — Moderate 4 — Major 5 — Critical
5 — Almost Certain510152025
4 — Likely48121620
3 — Possible3691215
2 — Unlikely246810
1 — Rare12345
07
Remediation Phase
Treat & Mitigate Risks

Apply the appropriate treatment strategy for each rated risk. Remediation isn't always the answer — the right response depends on cost, business context, and residual risk tolerance. Enforce an 8-stage review pipeline before any change touches production.

Remediation
isn't always
the right
answer.
🛠
Remediate
Fix the root cause. Patch, reconfigure, or remove.
🚫
Avoid
Eliminate the activity creating the risk entirely.
⬇
Mitigate
Reduce likelihood or impact through controls.
↔
Transfer
Shift risk via insurance or third-party contracts.
✓
Accept
Formally accept low residual risks with sign-off.
⚙ Tools I Use
RMMConnectWise Automate
EDRSentinelOne
MDRHuntress
PATCHWSUS
IAMAzure AD / Entra ID
PSAConnectWise Manage
✓ Checklist
✓
Assign treatment owner and due date to each risk
✓
Complete 8-stage script review before deployment
✓
Stage changes: test → pilot group → stagger rollout
✓
Document residual risk after treatment
✓
Obtain formal acceptance sign-off for retained risks
✓
Verify treatment effectiveness post-deployment
08
Continuous Improvement Phase
Monitor & Review

Risk is not static. Continuously monitor controls, track emerging threats, and review risk ratings on a defined cadence. A risk assessment that isn't revisited becomes a liability. Monthly trending, quarterly reviews, and post-incident reassessments keep the register accurate and actionable.

∞
Risk management is a continuous, not one-time, process
⚙ Tools I Use
SIEMGraylog
MONNagios
EDRSentinelOne
MDRHuntress
RMMConnectWise Automate
BDRDatto / Veeam
✓ Checklist
✓
Set monthly review cadence for high-rated risks
✓
Track 60-day patch compliance trending baselines
✓
Monitor SIEM alerts and escalation thresholds
✓
Conduct quarterly full risk register review
✓
Reassess after every significant incident
✓
Update risk register when new assets are onboarded