Most organizations depend on technology more deeply than their written plans suggest.

Email may carry approvals. A scheduling system may determine who receives service. Cloud storage may hold contracts, personnel files, grant records, or patient information. A customer relationship system may contain the history that allows staff to follow through. Accounting, payroll, billing, inventory, communications, security cameras, access controls, and specialized equipment may all depend on connected systems.

When technology works, those dependencies can be almost invisible.

When it stops working—or when information is exposed, altered, deleted, or held for ransom—the issue quickly becomes an organizational problem.

An IT plan should begin with the work, not the hardware

A useful IT risk-management plan begins by asking what the organization needs technology to accomplish.

Which services cannot operate without a particular system? Which records must remain accurate and available? Which information would cause harm if disclosed? Which vendors have access to data or essential processes? How long could each system be unavailable before the consequences became serious?

Those questions connect technology to mission, operations, legal obligations, and continuity.

An equipment list alone cannot do that.

A practical framework: NIST Cybersecurity Framework 2.0

The National Institute of Standards and Technology Cybersecurity Framework 2.0 provides a flexible structure for organizations of any size, sector, or level of technical maturity.

Its six functions create a useful management cycle:

  • Govern: Establish accountability, policies, priorities, legal and contractual requirements, vendor expectations, and risk tolerance.
  • Identify: Understand systems, data, devices, users, dependencies, vulnerabilities, threats, and business impact.
  • Protect: Apply safeguards such as access control, multifactor authentication, training, secure configuration, backups, updates, encryption, and data-handling practices.
  • Detect: Recognize unusual activity, failures, unauthorized access, malware, data loss, and other events early enough to respond.
  • Respond: Contain incidents, communicate, preserve information, meet reporting obligations, coordinate vendors, and make decisions under pressure.
  • Recover: Restore systems and data, validate that operations are safe, communicate with affected parties, and improve controls based on what occurred.

NIST also provides a more detailed Risk Management Framework with seven steps: Prepare, Categorize, Select, Implement, Assess, Authorize, and Monitor. That structure is important in federal and highly regulated environments. A small organization may use its logic without adopting every federal control or document.

What a basic IT risk-management plan should contain

The plan should be detailed enough to guide decisions but simple enough to maintain.

At a minimum, it should address:

  • Scope and ownership: Who has executive responsibility, who handles technical work, and who can make decisions during an incident?
  • Asset inventory: Systems, software, cloud services, devices, accounts, network equipment, websites, operational technology, and critical vendors.
  • Data inventory and classification: What information is collected, where it is stored, who can access it, how long it is retained, and what requirements apply?
  • Operational dependencies: Which business or service functions rely on each system, and how long can they tolerate an interruption?
  • Risk register: Threat, vulnerability, potential consequence, likelihood, impact, existing safeguards, owner, planned treatment, and review date.
  • Access management: Account approval, least-necessary access, multifactor authentication, privileged accounts, shared accounts, and prompt removal when roles change.
  • Protective maintenance: Updates, secure configuration, vulnerability remediation, endpoint protection, encryption, and physical safeguards.
  • Backups and restoration: What is backed up, frequency, separation from production systems, retention, responsibility, and documented restoration testing.
  • Vendor management: Contract responsibilities, access, security expectations, incident notification, data return or destruction, and alternatives if a service fails.
  • Incident response: How events are reported, assessed, contained, escalated, documented, communicated, and reviewed.
  • Continuity and recovery: Manual workarounds, alternate communications, system priorities, recovery objectives, and the point at which operations can safely resume.
  • Training, testing, and review: Staff awareness, exercises, restoration tests, lessons learned, and scheduled plan updates.

IT support and organizational accountability are not the same thing

An outside IT provider may install safeguards, monitor systems, manage devices, maintain backups, or respond to alerts.

Leadership still needs to decide:

Which operations and information are most important?

What downtime and data loss can the organization tolerate?

Which legal, contractual, insurance, and funder requirements apply?

Who is authorized to accept risk or shut down a system?

Who must be notified when an incident occurs?

A vendor can support those decisions. It should not silently make them on behalf of the organization.

Connect the IT plan to continuity planning

The IT risk plan and continuity plan should point to each other.

The continuity plan identifies the essential functions and the timeframes in which they must continue or resume. The IT plan identifies the systems, data, safeguards, vendors, backups, and recovery activities needed to support those functions.

If payroll must resume within three days, the organization should know which systems, bank connections, records, approvals, staff, vendors, and alternate procedures are required.

If a clinic must maintain continuity of care, it should understand how staff will access essential information, communicate, document services, protect privacy, and reconcile records after systems return.

A backup is not a recovery plan. Recovery requires tested restoration, assigned roles, decision criteria, communications, and a safe return to operation.

Requirements depend on the organization and its information

There is no single cybersecurity law that imposes the same plan on every small organization. Requirements depend on the industry, information, contracts, clients, funding, location, and services involved.

Examples include:

  • HIPAA Security Rule: Covered entities and business associates must conduct an accurate and thorough assessment of risks and vulnerabilities to electronic protected health information and implement reasonable and appropriate safeguards.
  • FTC Safeguards Rule: Covered financial institutions must maintain a written information-security program based on a written risk assessment and other required safeguards.
  • Washington breach-notification law: RCW 19.255.010 establishes notification requirements for businesses that own or license covered personal information when an applicable breach occurs.
  • Washington My Health My Data Act: Chapter 19.373 RCW establishes privacy and security requirements for consumer health data that may fall outside traditional HIPAA coverage.
  • Contracts and insurance: Customer agreements, business-associate agreements, grants, payment-card arrangements, cyber-insurance policies, and vendor contracts may create additional duties.

Organizations should identify applicable requirements before an incident, not while trying to determine whether notice is due.

Start with what is most consequential

A small organization does not need to solve every technology risk at once.

A useful first review can identify:

  • The five systems or services the organization depends on most
  • The most sensitive or consequential information it holds
  • Accounts with administrative or financial authority
  • Single points of failure involving one employee, device, vendor, connection, or location
  • Whether backups can actually be restored
  • Who would lead the first hour of a cyber or technology incident
  • Which gaps require immediate action and which can be scheduled

The goal is not a perfect binder. It is a visible, assigned, tested, and regularly reviewed approach to technology risk.

BERIDIAN helps organizations connect technology planning with the operational work technology supports. That can include documenting systems and dependencies, organizing an IT risk register, clarifying ownership, coordinating continuity and incident-response planning, reviewing vendor responsibilities, and creating maintainable tracking tools.

IT risk becomes more manageable when leadership can see the systems, decisions, dependencies, and responsibilities behind it.

Read the companion article: Risk Belongs Across the Organization: Enterprise Risk Management for Organizations of Every Size.

Sources and Further Reading

  1. National Institute of Standards and Technology. The NIST Cybersecurity Framework 2.0.
  2. National Institute of Standards and Technology. Risk Management Framework.
  3. National Institute of Standards and Technology. NIST Risk Management Framework Small Business Quick Start Guide.
  4. U.S. Department of Health and Human Services. Guidance on Risk Analysis Requirements under the HIPAA Security Rule.
  5. Federal Trade Commission. FTC Safeguards Rule: What Your Business Needs to Know.
  6. Washington State Legislature. Chapter 19.255 RCW, Personal Information—Notice of Security Breaches.
  7. Washington State Legislature. Chapter 19.373 RCW, Washington My Health My Data Act.

This article provides general operational information and is not legal, regulatory, cybersecurity, privacy, clinical, accounting, or insurance advice. Organizations should confirm the requirements applicable to their information, activities, industry, contracts, and jurisdiction with qualified professionals and the appropriate regulatory authorities.