Imagine it is 9:30 p.m. and your Hudson Valley business receives an alert about a suspicious Microsoft 365 sign-in. The office is closed, the employee is not answering and the account is used to send customer invoices. Who investigates, who can disable access and how will your team know it is safe to use again?
Cybersecurity incident response is the organized work of investigating a suspected attack, limiting its impact and coordinating a safe return to normal operations. It connects technical actions with business decisions, communication and follow-up, rather than stopping when an alert has been acknowledged. (CISA’s response and recovery guidance)
Before the next incident, decide who can authorize action, which business systems must recover first and who will confirm that staff can work again. Start with a short conversation between leadership and IT: “If a suspicious account or device is reported tonight, what happens next, and who makes the decisions?” Whether your office is in New Windsor, Newburgh, Middletown, Poughkeepsie, Kingston or Nyack, the planning questions are the same.
845-896-1800
Fisch Solutions team at the New Windsor operations center.
What a cybersecurity incident response plan covers
An incident response plan is a short written document that says who does what when a security problem is suspected. For a small business it can be a single page. Its value is that the decisions are made before anyone is under pressure.
NIST updated its incident response guidance in April 2025. The current publication, SP 800-61 Revision 3, encourages organizations to build incident response into their wider cybersecurity risk management. NIST says doing so “can help organizations prepare for incident responses, reduce the number and impact of incidents that occur, and improve the efficiency and effectiveness of their incident detection, response, and recovery activities.” (NIST SP 800-61 Rev. 3)
A working cyber incident response plan answers six questions:
- Who is on the response team, and how are they reached after hours?
- Who can approve containment, such as disabling an account or isolating a computer?
- Which systems must come back first?
- How will the team communicate if company email cannot be trusted?
- Who else needs to be involved, such as your attorney, cyber insurance carrier, key vendors and bank?
- How will the business confirm that recovery is complete?
The answers get longer as an organization grows. The questions do not change.
Start with facts, not just an alert notification
Ask your IT or security team to separate what is known from what is still being investigated. Request the affected account or system, the activity that triggered attention, any action already taken and the next update you should expect.
For example, use a suspicious sign-in as a planning exercise. Ask whether the login succeeded, whether the employee recognizes it, what information was available to the account and whether other activity needs review. Treat this as an exercise, not an assumption that every unfamiliar sign-in is a confirmed breach.
Agree on a short update format before an incident: what happened, what is affected, what has been done and what decision is needed. Avoid asking a business manager to interpret a raw technical alert without that explanation.
The five incident response steps, from alert to verified recovery
Ask your IT or security team to separate what is known from what is still being investigated. Request the affected account or system, the activity that triggered attention, any action already taken and the next update you should expect.
For example, use a suspicious sign-in as a planning exercise. Ask whether the login succeeded, whether the employee recognizes it, what information was available to the account and whether other activity needs review. Treat this as an exercise, not an assumption that every unfamiliar sign-in is a confirmed breach.
Agree on a short update format before an incident: what happened, what is affected, what has been done and what decision is needed. Avoid asking a business manager to interpret a raw technical alert without that explanation.
The five incident response steps, from alert to verified recovery
It helps to think of incident response steps in five stages. Each stage has a question the business should be able to answer.
- Alert. Which account or system is involved, and what triggered the alert?
- Investigation. What is known, and what is still being checked?
- Containment. Who can approve disabling an account or isolating a device?
- Recovery. Which systems return first, and from which backup?
- Business verification. Who tests the restored systems and signs off?
Acknowledging an alert completes the first stage only. A plan covers all five.
The five incident response steps, from alert to verified recovery
It helps to think of incident response steps in five stages. Each stage has a question the business should be able to answer.
- Alert. Which account or system is involved, and what triggered the alert?
- Investigation. What is known, and what is still being checked?
- Containment. Who can approve disabling an account or isolating a device?
- Recovery. Which systems return first, and from which backup?
- Business verification. Who tests the restored systems and signs off?
Acknowledging an alert completes the first stage only. A plan covers all five.
Decide who can authorize containment
Document which protective actions your team can take immediately and which require a business decision. Include an alternate decision-maker so the process does not depend on one person answering a call.
Use practical questions when setting that authority:
- Account access: Who can approve disabling an account used for billing, payroll or customer communication?
- Device isolation: What should happen if the affected computer supports a shared business function?
- Outside assistance: Who can engage an application vendor or specialist when the problem extends beyond the regular support team?
- Communication: How will the team reach leadership if company email cannot be trusted?
Keep a verified phone contact and an alternative communication method in the plan. Test that the people named in it know their role rather than assuming a contact list is enough.
A password reset may be only part of the work
Microsoft’s guidance for a compromised Microsoft 365 account includes blocking access, revoking sign-in sessions, reviewing registered authentication methods, checking forwarding and inbox rules, and investigating logs. Its response procedure goes beyond changing the password. (Microsoft’s compromised-account guidance)
Use that distinction when discussing an account incident with your technical team. Ask what access was removed, what was reviewed, what remains uncertain and what needs to happen before the account is returned to normal use.
Do not turn this into a do-it-yourself repair exercise for the affected employee. Route the work through the authorized administrator or response team, and agree on a trusted way to communicate with the employee during the investigation.
Incident response, disaster recovery and business continuity are different plans
These three plans are often discussed as if they were one document. They answer different questions, and a business needs an answer to each.
| Plan | Question it answers | Example |
|---|---|---|
| Incident response plan | What do we do when we suspect a security problem? | A suspicious sign-in is investigated, the account is disabled and its activity is reviewed. |
| IT disaster recovery plan | How do we restore systems and data, and in what order? | The accounting server is restored from backup and tested before staff return to it. |
| Business continuity plan | How does the business keep operating while systems are down? | Staff take orders by phone and on paper until the order system is back. |
Backup vs. disaster recovery is the same kind of distinction. A backup is a copy of your data. A disaster recovery plan is the tested process for turning that copy back into a working system, including who performs the restore, where it runs and how the result is checked.
Plan IT disaster recovery around Hudson Valley business operations
For IT disaster recovery in the Hudson Valley, start with the work people need to perform, not simply a list of servers. Ask each department to identify its essential applications, the information it needs and any temporary way to operate without them.
Backups alone are not a recovery plan. Plan who will restore the data, where it will run, which systems must return first and how staff will verify that the restored environment supports their work.
Set two objectives: the recovery time objective (RTO) is how quickly a system needs to be restored before the interruption becomes unacceptable to the business; the recovery point objective (RPO) defines how far back in time the recovered data can be, expressing how much recent data loss the business can tolerate. (NIST’s RTO definition, NIST’s RPO definition) Treat these as planning targets to test, not guaranteed recovery results.
For IT disaster recovery in the Hudson Valley, start with the work people need to perform, not simply a list of servers. Ask each department to identify its essential applications, the information it needs and any temporary way to operate without them.
Backups alone are not a recovery plan. Plan who will restore the data, where it will run, which systems must return first and how staff will verify that the restored environment supports their work.
A simple way to remember RTO vs. RPO: the recovery point objective looks back from the incident to the last usable backup, and the recovery time objective looks forward to the moment systems are restored and verified.
Consider a manufacturing business as a planning example, not a customer case study. Restoring a shared folder would be only one task; the exercise should also test whether authorized employees can access the scheduling application, retrieve the right records and complete their normal work.
Build the recovery discussion around four decisions:
- Business priority: Which function must return first, and who owns that decision?
- Recovery dependencies: What accounts, applications, network connections and vendors does that function rely on?
- Acceptable interruption: What downtime and data-loss objectives should guide the recovery design?
- Business validation: Who will test the restored function and confirm it is ready for use?
CISA recommends planning for restoration of critical systems, aligning backups with recovery objectives and testing backups regularly. It also recommends considering how essential functions could continue without normal systems or internet access. (CISA’s small-business security guidance)
Use a recovery exercise to check those assumptions. Record what worked, what access or documentation was missing and what needs to change before the next test.
Five incidents to walk through before they happen
Use these five scenarios as tabletop exercises. Pick one, gather the people who would be involved and talk through what would happen, step by step.
A compromised Microsoft 365 or Google Workspace account
This is the practical answer to what to do if your email is hacked. Report it to your administrator or IT provider through a channel other than the affected mailbox. The steps Microsoft describes above are the model: block access, end active sessions, review forwarding and inbox rules, and check what the account could reach. Ask the same questions about a Google Workspace account. Decide in advance who tells customers or vendors if messages were sent from the account.
Ransomware
CISA’s ransomware guide starts with scope: “Determine which systems were impacted, and immediately isolate them.” Ransomware recovery then depends on backups the attack could not reach. The same guide advises organizations to “Maintain offline, encrypted backups of critical data, and regularly test the availability and integrity of backups in a disaster recovery scenario.” (CISA’s #StopRansomware Guide) Walk through who would isolate the affected computers, where the offline backup is kept and who would decide the order of restoration.
Business email compromise
Business email compromise is a fraud in which a criminal impersonates a vendor, executive or employee to redirect a payment. The FBI advises verifying payment and purchase requests in person if possible, or by calling the person to make sure the request is legitimate. If a payment has already been sent, the FBI’s instruction is direct: “You should also contact your financial institution immediately and request that they contact the financial institution where any transfer was sent.” It also directs businesses to report the scam at ic3.gov, the FBI’s Internet Crime Complaint Center. (FBI guidance on business email compromise) Decide now who calls the bank and where its fraud contact number is kept.
A lost or stolen laptop
Ask what was on the device, whether its drive was encrypted and whether it can be locked or wiped remotely. Reset the passwords and end the sign-in sessions for the accounts used on it. Record when it was last seen and who was told.
A vendor or cloud outage
Not every incident is an attack. If your internet provider, phone system or a cloud application goes down, the business continuity plan takes over. Identify who contacts the vendor, how staff keep working in the meantime and how customers will reach you.
Keep a record of decisions and unfinished work
Make the incident record useful to both technical staff and leadership. Capture the timeline, affected systems, approvals, actions taken, restoration checks and the person responsible for each remaining task.
Separate a completed action from an unresolved question. For example, record “account disabled” as an action, then track the investigation of account activity as its own item rather than treating the first step as closure.
Where legal, insurance or reporting questions arise, involve the appropriate adviser. Keep technical findings available for those decisions without presenting an IT status update as a legal determination or an insurance coverage decision.
Fisch’s technical IT compliance services include implementation and documentation support for applicable requirements, distinct from independent assessment or certification decisions. Keep that distinction clear when assigning the work.
A one-page incident response checklist for Hudson Valley small businesses
Small business cybersecurity planning does not need a binder. Answer these ten questions, put the answers on one page and keep a printed copy where it can be found without a computer.
- Who is the first call when something looks wrong?
- Who can approve disabling an account or isolating a device, and who is the alternate?
- Which three to five systems must come back first?
- Where are the backups, and when was a restore last tested?
- What are the recovery time objective and recovery point objective for each of those systems?
- How will the team communicate if email is unavailable?
- Who calls the bank if a payment may have been redirected?
- Who are the contacts at your cyber insurance carrier and your attorney?
- Which vendors need to be reached, and how?
- Who confirms that each department can work again?
Review the page whenever a named person, vendor or system changes.
Connect monitoring with the people who can carry out the work
Fisch’s fully managed or co-managed IT support brings together help desk, engineering, cybersecurity, compliance and field resources from its New Windsor headquarters for Hudson Valley organizations. Start the discussion with the work your internal team already handles and the additional help it needs.
Fisch’s cybersecurity services connect monitoring with investigation, authorized response and follow-up, using its local SOC team during business hours and a partner SOC after hours to provide 24/7 monitoring for covered systems. Confirm which systems and response arrangements apply to your business.
Before an incident, confirm who owns monitoring, containment, technical remediation and recovery. Record customer approvals and any specialist involvement in the service arrangements; do not assume that monitoring automatically includes every part of recovery.
Questions about incident response and recovery
A cybersecurity incident response plan is a written document that sets out who investigates a suspected security problem, who can approve protective action, which systems are restored first and how the business confirms it is safe to resume work.
This article uses five: alert, investigation, containment, recovery and business verification. The last stage matters as much as the first. The people who use a system confirm that it works before the incident is closed.
The recovery time objective (RTO) is how quickly a system needs to be restored. The recovery point objective (RPO) is how much recent data the business can afford to lose, measured back to the last usable backup. Both are planning targets to test, not guarantees.
No. A backup is a copy of data. A disaster recovery plan covers who restores it, where it runs, the order in which systems return and how staff verify the result.
Test it on a schedule your leadership agrees to, and again after a major change in staff, systems or vendors. A cybersecurity tabletop exercise is a practical format: the people named in the plan talk through a realistic scenario. CISA publishes Tabletop Exercise Packages, which it describes as “a comprehensive set of resources designed to assist stakeholders in conducting their own exercises.” (CISA Tabletop Exercise Packages)
Whether and when your business must notify anyone is a legal question, and the answer depends on the information involved and the people affected. The New York Attorney General receives reports of data breaches, and its data breach reporting page notes that the SHIELD Act strengthens New York’s data-security laws. Your data breach response plan should name the attorney who will make that determination. An IT status update is not a legal opinion.
A small business has fewer people to absorb an interruption, so knowing who to call and who can decide matters more, not less. The plan can be one page. The checklist above is a starting point.
Yes. Fisch Solutions works with organizations in Orange, Dutchess, Ulster, Rockland, Putnam, Westchester, Columbia and Sullivan counties on response contacts, authorization, critical systems and recovery priorities. For covered systems, its local SOC team monitors during business hours and a partner SOC monitors after hours. The services and response arrangements that apply to your business are defined in your agreement.


