Skip down to the research record

2 CISA ransomware guide sections for a forecast file

Quota Forecast Editorial Team · Published · 11 min read

Two sections of the CISA ransomware guide map directly onto keeping a shared-drive or laptop forecast file recoverable before quarter end: Part 1 for reducing likelihood and impact before an incident, and Part 2 for responding once one hits.

  • Part 1 tells you to conduct regular vulnerability scanning to identify and address vulnerabilities, especially on internet-facing devices, to limit the attack surface.
  • Part 1 also tells you to disable ports and protocols not used for business, with Remote Desktop Protocol (RDP) on TCP Port 3389 given as the example.
  • CISA offers a no-cost Vulnerability Scanning service and other no-cost assessments through its cyber resource hub.
  • Part 2 is a checklist of best practices for responding, so the first hour after an incident has a written path rather than an improvised one.
  • Deletion and ransomware are different events, but both end with you needing a restore path, and the IRS says to check before you discard records in case another purpose requires them longer.

Key takeaways

  • The CISA #StopRansomware Guide splits into two parts: Part 1 for reducing likelihood and impact, and Part 2 for responding.
  • Your forecast file on a shared drive or rep laptop is the asset both parts protect and recover.
  • Part 1 tells you to scan for vulnerabilities and close unused ports before an incident.
  • Part 2 gives you a checklist to run the moment files are encrypted or held.
  • Deletion and ransomware are different events, but both end with you needing a restore path.
  • The IRS says to check before discarding records past tax use in case another purpose requires them longer.

Who this is for

You keep a forecast file on a shared drive or a rep laptop. You need it back before quarter end. This post reads two sections of the CISA ransomware guide through that lens. It is written for revenue leaders, not security staff.

The guide is an update to the Joint Cybersecurity and Infrastructure Security Agency (CISA) and Multi-State Information Sharing & Analysis Center (MS-ISAC) Ransomware Guide released in September 2020, developed through the Joint Ransomware Task Force. You can read it at CISA's #StopRansomware Guide.

The guide says ransomware actors have accelerated their tactics and techniques since the initial release in September 2020. Your forecast file sits in the blast radius of that change. You do not need to become a security engineer to act on two sections of it.

What the two sections are

The two sections you need are Part 1 and Part 2 of the guide. Part 1 provides guidance for all organizations to reduce the impact and likelihood of ransomware incidents and data extortion, including best practices to prepare for, prevent, and mitigate these incidents. Part 2 includes a checklist of best practices for responding to these incidents.

Those two descriptions are the whole frame. Part 1 is what you do before anything happens. Part 2 is what you do after something does. For a forecast file, Part 1 is about making sure the file is recoverable. Part 2 is about what you run when it is not.

Here is how the two parts compare on the questions a revenue leader cares about.

Guide sectionWhat it coversYour forecast file
Part 1Reducing likelihood and impact before an incidentBackups, access, and storage choices you make now
Part 2A checklist for responding to an incidentThe steps you run when ransomware encrypts or holds the file; an accidental deletion follows a restore path instead

Part 1: make the file recoverable before you need it

Part 1 tells you to reduce the likelihood and impact of ransomware before it touches your file. Two specific instructions in the guide bear directly on a forecast file sitting on a shared drive or a laptop.

The first is this: conduct regular vulnerability scanning to identify and address vulnerabilities, especially those on internet-facing devices, to limit the attack surface, tagged in the guide as [CPG 1.E]. A laptop that syncs your forecast and a shared drive that holds it are both devices with an attack surface. Scanning them is Part 1's standing instruction.

The second is narrower and more concrete: disable ports and protocols that are not being used for business purposes, with Remote Desktop Protocol (RDP) on TCP Port 3389 given as the example, tagged as [CPG 2.X]. If your team does not use RDP for business, the guide says to disable it. An open unused port on a machine that holds your forecast is a door you are not using.

You do not have to fund a scanner yourself to start. CISA offers a no-cost Vulnerability Scanning service and other no-cost assessments through its cyber resource hub, tagged as [CPG 1.F]. That is a Part 1 action you can take this week without a budget cycle.

The practical read for a revenue leader is this. Part 1 is where you decide where the forecast file lives and who can reach it. A file that only exists on one rep's laptop is a file with one copy. A file on a shared drive that nobody scans is a file on a device the guide asks you to scan. Both are Part 1 gaps, and both are fixable before quarter end.

Part 1 covers preparing for, preventing, and mitigating incidents. The guide's purpose for Part 1 is to reduce the impact of an incident, and impact on a forecast file means the difference between restoring it and rebuilding it from memory. If your forecast lives in one place, you are one encryption event away from a manual rebuild. If it lives in a place with a restore path, you are one restore away from Tuesday morning.

You should ask your IT owner two plain questions this week. First: where does the forecast file live, and is that device on a scan? Second: does that machine expose any port nobody uses for business? Those questions map directly onto the two Part 1 instructions above.

Part 2: the checklist when ransomware hits

Part 2 is a checklist for responding. The guide says it includes a checklist of best practices for responding to these incidents. For a revenue leader, the value of Part 2 is that you do not have to invent a response while your quarter is on fire.

The checklist exists so that the first hour after an incident has a written path. Your job as the forecast owner is to know where that path is and who runs it. You do not need to memorize the checklist. You need to know that it exists, where to find it, and who on your team has read it.

Two things a revenue leader should have ready before Part 2 is ever needed. First, the name of the person who will run the response. Second, the location of the forecast file's restore path. Both are answers you give in the moment, and both are easier to give if you have written them down in a quiet week.

Part 2 also has a boundary worth naming. The guide's Part 2 is about responding to a ransomware incident. A file you deleted yourself by accident is a different event with a different path. The two overlap only in that both end with you wanting the file back.

That distinction matters because a forecast file can go missing in both ways. A rep can overwrite a tab. A system process can bulk-delete rows. And an incident can encrypt the whole thing. Each has its own restore story, and you should know which story applies before you pick up the phone.

What a deleted record tells you about restore paths

Microsoft's Dataverse documentation says users often delete records through regular business processes. Users often delete records or transactions either manually or systematically, either planned or by accident, through system processes, single selection, multiple selections, and bulk deletion. That range is wider than a single mis-click.

The same documentation tells you that you can proactively manage the storage used by deleted records. That is a storage control, not a restore guarantee, and you should read it as such. The page is Microsoft's guidance on restoring deleted Dataverse table records.

The lesson for a forecast file is plain. A forecast file that lives only in a live system, with no restore path, is exposed to all four. A forecast file with a managed restore path turns a bad afternoon into an admin task.

Ask your systems owner where deleted forecast rows go, how long they are retained, and who can trigger a restore. Those three answers tell you whether a bad click is a five-minute fix or a quarter-end rebuild. The source above does not state a retention window for your configuration, so your systems owner is the right person to ask.

The IRS rule that keeps old forecast files around

The IRS says that when your records are no longer needed for tax purposes, you should not discard them until you check to see if you have to keep them longer for other purposes. That is a check-before-you-delete rule. You can read it on the IRS page How long should I keep records?.

For a forecast file, the rule reads this way. Your forecast history is a record. Before you purge last quarter's file to clean up a drive, check whether anything else requires you to keep it. Contract audits, board reporting, and dispute files are examples this post offers of other purposes to weigh.

This matters for ransomware in a way that is easy to miss. A purge that was fine last quarter can remove the only copy of a forecast you now need to evidence. The IRS rule asks you to check first. Part 1 asks organizations to prepare for and mitigate incidents. The two point the same direction: do not be the person who deleted the file you needed.

Putting both sections on your forecast file

You can run the two sections as one short exercise this week.

Find the file. Write down where the forecast file lives. Shared drive, rep laptop, or both. If it is both, note which copy is authoritative. If you cannot name one, that is your first gap.

Scan the devices. The guide asks for regular vulnerability scanning, especially on internet-facing devices, and points to CISA's no-cost Vulnerability Scanning service. Put the drive's host and the rep laptops that sync the file on a scan.

Close unused doors. Check for ports and protocols not used for business. The guide's own example is RDP on TCP Port 3389. If your team does not use it, disable it.

Confirm a restore path. Ask where deleted records go and who can restore them. If your forecast is hosted in Dataverse, the Microsoft page linked above is the model question to ask; your systems owner holds the answer for your stack.

Check before you purge. Before deleting an old forecast file, apply the IRS check: is any other purpose requiring you to keep it?

Locate Part 2. Open the guide, find the Part 2 response checklist, and write down who runs it. You want that name on paper before an incident, not during one.

That is the whole exercise. The scanning step runs on CISA's no-cost service.

What the sources do not settle

One question the sources leave open: how long your specific forecast file must be retained under your contracts and your own reporting rules. The IRS page gives a check-before-delete rule, not a retention schedule for a forecast. Your legal or finance owner is the right person to ask.

FAQ

What is the CISA ransomware guide? It is the #StopRansomware Guide, an update to the Joint CISA and MS-ISAC Ransomware Guide released in September 2020, developed through the Joint Ransomware Task Force. It has two parts: Part 1 for reducing likelihood and impact, and Part 2 as a response checklist.

Why does a forecast file need Part 1 attention? Part 1 covers reducing the likelihood and impact of an incident. A forecast file on a scanned, closed-down device with a restore path has a very different impact profile than one that does not.

What is the concrete Part 1 action for a laptop? Two of its Part 1 actions bear directly on a laptop: regular vulnerability scanning to limit the attack surface, and disabling ports and protocols not used for business, with RDP on TCP Port 3389 as its example.

Can I use CISA's scanning for free? CISA offers a no-cost Vulnerability Scanning service and other no-cost assessments through its cyber resource hub.

What do I actually do in the first hour? Find the Part 2 response checklist in the guide and hand it to the person you named beforehand. Part 2 exists so the first hour has a written path rather than an improvised one.

How is a mis-click different from an incident? Microsoft's documentation describes deletion through system processes, single selection, multiple selection, and bulk deletion as ordinary business use. An encryption incident runs through the Part 2 checklist instead.

Should I delete old forecast files to save space? The IRS says to check first: do not discard records until you check whether you have to keep them longer for other purposes. Storage cleanup waits on that check.

Who owns this inside a revenue team? The forecast owner does. Security runs the scans and the response. Your job is to know where the file lives, who restores it, and who runs Part 2 when the file does not.

Sources