Small and medium-sized enterprises (SMEs) face persistent cybersecurity risks but often lack the budget, staffing, and specialist expertise required for broad, simultaneous implementation of cybersecurity controls. The NIST Cybersecurity Framework (CSF) 2.0 provides a flexible structure for managing cyber risk, yet SMEs still need an operational method for translating framework outcomes into achievable work. This article proposes the Agile-CSF SME Implementation Model, a phased and risk-prioritized approach that integrates the six CSF 2.0 Functions—Govern, Identify, Protect, Detect, Respond, and Recover—with security backlogs, user stories, short delivery sprints, review cycles, and measurable outcomes. The model begins with governance and critical-asset identification, advances to high-impact protection and detection, and then establishes streamlined response and recovery capabilities. It also defines a Minimum Viable Security Program for engaging managed security service providers and suggests practical metrics for monitoring implementation progress. The proposed model is intended as a practical design framework that organizations can tailor to their risk profile, regulatory obligations, and available resources.
Key index in this article : Agile, cybersecurity governance, NIST CSF 2.0, small and medium-sized enterprises, SME cybersecurity, cyber risk management, managed security service provider, security backlog.
I. INTRODUCTION
Small and medium-sized enterprises are increasingly
dependent on cloud applications, digital payments, remote work, third-party
services, and interconnected business processes. This dependence expands the
potential impact of credential theft, ransomware, data loss, service
interruption, and supply-chain compromise. At the same time, many SMEs operate
without a dedicated security operations center, mature governance function, or
substantial control-implementation budget.
The National Institute of Standards and Technology released
Cybersecurity Framework 2.0 as a flexible, outcome-oriented resource for
organizations of any size, sector, or maturity. CSF 2.0 organizes cybersecurity
outcomes through six Functions: Govern, Identify, Protect, Detect, Respond, and
Recover. The addition of Govern emphasizes that cybersecurity risk should be
directed through organizational context, policy, roles, oversight, and
supply-chain considerations rather than treated solely as a technical matter.
For an SME, however, the breadth of the framework can create
an execution challenge. Attempting to address every outcome at once may lead to
excessive planning, fragmented tool purchases, and limited completion. Agile
principles offer a complementary execution model: prioritize value and risk,
divide work into manageable increments, review outcomes frequently, and adapt
the backlog as conditions change.
This article proposes the Agile-CSF SME Implementation
Model. The model does not modify or replace CSF 2.0. Instead, it provides a
delivery mechanism for translating selected CSF outcomes into prioritized,
measurable improvement work. The model is designed for practical adoption and
should be tailored to applicable legal, contractual, regulatory, and industry
requirements.
A. Contributions
- A
phased sequencing model that begins with governance and critical-asset
visibility, progresses to high-impact protection and detection, and then
strengthens response and recovery.
- A
security-backlog structure that converts risk findings and CSF outcomes
into prioritized epics, user stories, acceptance criteria, owners, and
sprint deliverables.
- A
Minimum Viable Security Program (MVSP) model for outcome-focused
collaboration with a managed security service provider (MSSP) or taken by
internal team within the SME.
II. BACKGROUND AND DESIGN CONTEXT
A. NIST CSF 2.0
CSF 2.0 consists of the Core, Organizational Profiles, and
Tiers. The Core identifies cybersecurity outcomes; Profiles help an
organization describe current and target outcomes; and Tiers characterize the
rigor of cybersecurity risk governance and management practices. NIST also
provides a Small Business Quick-Start Guide that emphasizes understanding
organizational context, identifying critical services and assets, protecting
access and data, monitoring events, preparing for incidents, and planning recovery.
B. Agile as an Execution Mechanism
Agile methods favor iterative delivery, stakeholder
collaboration, visibility of work, and adaptation to changing conditions. In
cybersecurity, these characteristics can be applied through a prioritized risk
backlog, time-boxed implementation, demonstrable control outcomes, and
retrospective learning. Agile execution should not be confused with lowering
control rigor. Each completed item should satisfy defined acceptance criteria
and produce auditable evidence where required.
C. Scope and Intended Use
The model is intended for SMEs and other
resource-constrained organizations seeking a structured starting point. It is
not a certification scheme, legal opinion, penetration-testing method, or
substitute for a formal risk assessment. Organizations in regulated sectors
should map the model to applicable obligations and obtain qualified legal,
compliance, privacy, and cybersecurity advice.
III. THE AGILE-CSF SME IMPLEMENTATION MODEL
The model uses five recurring steps: establish context,
prioritize outcomes, implement in short sprints, verify results, and adapt the
backlog. Work is prioritized through risk and business value rather than by the
order in which controls appear in a catalogue.
|
Model Stage |
Primary CSF Functions |
Agile Mechanism |
Expected Evidence |
|
1. Establish direction |
Govern |
Leadership objective, risk tolerance, ownership, initial
target profile |
Approved scope, accountable owner, risk criteria |
|
2. Build visibility |
Identify |
Asset and risk backlog, dependency mapping |
Prioritized inventory, risk entries, data flows |
|
3. Reduce highest risks |
Protect and Detect |
User stories and sprint delivery |
Configured controls, test records, alert evidence |
|
4. Prepare for disruption |
Respond and Recover |
Scenario stories, exercises, restoration tests |
Incident plan, contact tree, exercise and restore results |
|
5. Improve continuously |
All Functions |
Review, retrospective, backlog reprioritization |
Metrics, lessons learned, updated target profile |
A. Backlog Prioritization
Each candidate security item should be scored consistently.
A simple five-factor method uses a 1-to-5 scale for business criticality,
threat exposure, regulatory or contractual urgency, expected risk reduction,
and implementation effort. Higher criticality, exposure, urgency, and risk
reduction increase priority; higher effort reduces it. One transparent
prioritization formula is shown in below :
Priority Score = (Criticality + Exposure + Urgency + Risk
Reduction) / Effort
The formula is a decision aid, not a substitute for expert
judgment. Immediate safety, legal, active-incident, or material business risks
should be escalated outside the normal sprint queue.
B. Security User Stories and Acceptance Criteria
Security work should be expressed in business terms with
testable completion conditions. Example: “As the owner of a critical cloud
service, I want multi-factor authentication enforced for all privileged
accounts so that stolen passwords alone cannot provide administrative access.”
Acceptance criteria may include: all privileged accounts identified; MFA
enforced; emergency-access accounts separately controlled and monitored;
unsuccessful enrollment exceptions resolved; and configuration evidence retained.
IV. INTEGRATED IMPLEMENTATION
A. Phase 1: Govern and Identify
Leadership first defines the business services in scope,
risk tolerance, accountable roles, escalation paths, and priorities. The team
then creates a prioritized inventory of critical data, applications, devices,
identities, vendors, and dependencies. The target is not an exhaustive
enterprise inventory on day one. The first increment should provide sufficient
visibility to identify the assets whose compromise or unavailability would
cause the greatest business impact.
B. Phase 2: Protect and Detect
The next sprints implement controls with high expected
risk reduction. Typical candidates include MFA for privileged and remote
access, least-privilege administration, secure configuration, endpoint
protection, encryption where appropriate, reliable patching, phishing-resistant
practices, employee awareness, centralized logging, alerting for suspicious
sign-ins, and tested escalation procedures. Selection should be based on the
organization’s threat exposure and critical services, not on a generic tool list.
C. Phase 3: Respond and Recover
The organization establishes a concise incident-response
plan that identifies decisionmakers, technical contacts, external support,
legal and regulatory escalation, customer communication responsibility, and
evidence-preservation need. Recovery work should identify critical restoration
priorities, backup ownership, recovery objectives, offline or isolated backup
arrangements where appropriate, and scheduled restoration tests. A backup
should not be considered reliable until restoration has been demonstrated.
V. COST-CONSCIOUS CONTROL SELECTION
Resource constraints make control sequencing particularly
important. SMEs should first evaluate security capabilities already included in
their cloud, identity, endpoint, networking, and backup services. Examples may
include MFA, conditional-access features, native audit logs, mail filtering,
device encryption, security baselines, and administrative alerts. Capabilities
and licensing change over time; therefore, product availability and cost must
be verified directly with the provider before implementation.
Open-source or lower-cost products may support password
management, vulnerability assessment, log aggregation, DNS filtering, backup,
and endpoint monitoring. The choice should consider not only acquisition cost
but also deployment effort, maintenance, secure configuration, supportability,
data handling, and the skills required to operate the product. An unmanaged
“free” tool can create more risk than a smaller set of well-operated controls.
VI. AGILE ENGAGEMENT MODEL
The SME can either implement CSF 2.0 suggested focused
areas or An MSSP can be approached to provide expertise and operational
capacity that an SME cannot economically maintain internally. In this paper we
take the approach of a MSSP getting into engagement with SME. The relationship
should begin with a Minimum Viable Security Program: the smallest coherent set
of governance, visibility, protection, detection, response, and recovery
outcomes required to reduce the most material risks.
- Baseline
sprint: Confirm scope, critical services, current profile, known risks,
responsibilities, and evidence gaps.
- Outcome-based
backlog: Prioritize tangible outcomes such as privileged-account MFA,
backup restoration, alert configuration, vulnerability remediation, or
incident exercise.
- Short
review cadence: Review completed evidence, unresolved risks, service
performance, new threats, and next-sprint priorities every two to four
weeks.
- Clear
accountability: Document which responsibilities remain with the SME, which
are assigned to the MSSP, and which are shared. Outsourcing execution does
not eliminate organizational accountability.
- Maturity
progression: Use CSF Tiers and Current/Target Profiles to communicate
progress, while avoiding the interpretation that Tiers are certification
levels.
VII. MEASUREMENT
Metrics should demonstrate risk reduction and operating
discipline rather than activity volume alone. A balanced initial scorecard is
shown in Table II.
|
Metric Example |
Definition |
Management Use |
|
Critical-asset coverage |
Critical assets with assigned owner and risk
classification / identified critical assets |
Shows visibility and accountability |
|
Privileged MFA coverage |
Privileged accounts protected by approved MFA / total
privileged accounts |
Tracks reduction of credential risk |
|
Security backlog age |
Median days unresolved for high-priority security items |
Identifies delivery or ownership bottlenecks |
|
Risk lead time |
Days from risk acceptance into backlog to verified
control completion |
Measures responsiveness |
|
Detection coverage |
Priority threat scenarios with tested alerts / selected
priority scenarios |
Shows whether monitoring addresses relevant threats |
|
Restore success rate |
Successful scheduled restoration tests / restoration
tests attempted |
Provides evidence of recoverability |
|
Exercise completion |
Planned incident exercises completed with documented
lessons |
Measures preparedness and learning |
IX. DISCUSSION AND LIMITATIONS
The model offers three practical advantages. First, it
reduces implementation paralysis by defining a defensible starting sequence.
Second, it creates traceability between business risk, CSF outcomes, backlog
items, and completion evidence. Third, it supports adaptive investment because
priorities can change as threats, services, regulations, and organizational
capabilities evolve.
The model also has limitations. It is a conceptual and
practice-oriented framework and has not been empirically validated in this
article. SMEs vary substantially by sector, data sensitivity, geography,
technology architecture, and regulatory obligations. Future work should
evaluate the model through execution approach , model through
multi-organization case studies, compare implementation outcomes against
alternative approaches, and examine which metrics best predict sustained risk
reduction.
X. CONCLUSION
NIST CSF 2.0 provides a broad and flexible structure for
managing cybersecurity risk, but resource-constrained organizations need a
practical execution mechanism. The Agile-CSF SME Implementation Model
translates selected framework outcomes into a prioritized backlog, short
implementation cycles, verified deliverables, measurable progress, and
continuous reprioritization. By beginning with governance and visibility,
implementing high-impact protection and detection, and validating response and
recovery, an SME can develop cybersecurity capability progressively rather than
approaching the framework as an all-or-nothing compliance project. The model’s
value depends on honest risk assessment, accountable ownership, evidence-based
completion, and adaptation to the organization’s specific obligations and
operating environment.
REFERENCES
- [1]
National Institute of Standards and Technology, “The NIST Cybersecurity
Framework (CSF) 2.0,” NIST CSWP 29, Feb. 2024, doi: 10.6028/NIST.CSWP.29.
- [3]
National Institute of Standards and Technology, “NIST Cybersecurity
Framework 2.0: Small Business Quick-Start Guide,” NIST SP 1300, 2024, doi:
10.6028/NIST.SP.1300.
- [4]
National Institute of Standards and Technology, “Cybersecurity Framework
2.0 Resource and Overview Guide,” NIST SP ... (cut off at end of paste)
