Skip to content
CTS Field Notes

CTS Field Notes

Overlooked problems, assumptions worth questioning, and things worth knowing.

Practical technology judgment for business leaders. Fresh perspectives for curious minds.

Who Unlocked the Sample Files?

Imagine that your business has been hacked and its files encrypted. You hire a firm that says it can help with this exact issue using proprietary software to decrypt the data. You send two encrypted files to the ransomware recovery firm, and those files come back readable. With operations disrupted and more data still out of reach, that demonstration gives your business a reason to authorize the larger recovery job. Should that help build trust? Do you want to know what is happening behind the scenes?

Consider the real-life case of MonsterCloud. Federal prosecutors allege that, in many cases involving the company, the people who opened those samples were the same people who had locked them. The firm’s owner then returned the samples to customers as evidence of its recovery capabilities.

What prosecutors allege MonsterCloud promised

MonsterCloud is a Florida ransomware recovery company. Prosecutors allege that its owner, Zohar Pinhasi, marketed proprietary technology that could recover encrypted files without paying attackers. They say he instead secretly paid attackers for decryption keys, using part of the fees customers paid his company.

That is the alleged deception: selling customers one explanation of how their files would be recovered while concealing another. The charges concern alleged fraud against recovery customers, not an allegation that Pinhasi carried out the original ransomware attacks. Federal indictment.

On October 7, Pinhasi pleaded not guilty to one count of conspiracy to commit wire fraud and two counts of wire fraud. The charges are allegations, and he is presumed innocent. The public docket reviewed on November 11 listed a November 9 status conference and a continuance order, followed by a letter filed November 10 whose contents were unavailable in the public mirror. Court docket and arraignment minutes.

In a 2019 interview with ProPublica, Pinhasi said MonsterCloud did not mislead clients or promise a particular recovery method. That was his position years before the indictment. ProPublica investigation.

The contracts add another distinction. According to the indictment, some allowed contact with or payment to attackers, sometimes only after other recovery options were exhausted. Prosecutors allege that contacting the attackers was generally Pinhasi’s first step.

What a successful sample test tells you

Two readable files give a customer something useful to examine. They do not, by themselves, establish where the decryption capability came from or whether the remaining files can be restored.

A customer should open returned samples in the applications that use them and have someone familiar with the records check their contents. A spreadsheet that opens but is missing information may not help the business resume operations.

The recovery vendor should also explain how it obtained the means to open the files. Was it restoring a backup, using an available decryption tool, or working with the attacker? Who received the samples? What does that result establish about the remaining data?

Those questions do not require a vendor to reveal its software. They ask for enough information to understand and authorize the work.

Choose the recovery vendor before you need one

A business whose systems are down has little patience for checking references and comparing contract language. Every additional hour creates pressure to accept the first credible promise of recovery.

Do that work while the business is running normally. Identify who you would call, speak with them, and understand what their role would be. If you carry cyber insurance, check the policy’s notification and vendor-approval requirements before committing to a provider.

A useful conversation goes beyond “Can you get our files back?”

  • Who will do the work? Identify the company, the response team and any subcontractors. Ask for independently checkable references from comparable incidents.
  • What are we buying? Clarify whether the engagement covers file recovery alone or also investigating the intrusion, containing it and helping the business restore safe operations.
  • What needs our approval? Set written rules for sharing files, contacting attackers, making payments and expanding the work. Name the person at your company who can authorize each step.
  • How will we know what happened? Agree on progress reports, recovery tests and a bill that distinguishes the vendor’s services from outside payments.

Keep those answers and contact details somewhere accessible if company systems are unavailable. Review them when vendors, insurance coverage or key staff change.

None of this guarantees an honest vendor or a successful recovery. It gives the business time to examine claims, understand limitations and resolve uncomfortable questions before a shutdown makes every answer feel urgent.

The sample files matter. So does knowing whose hands they passed through. The best time to establish how a recovery vendor earns your trust is before you are depending on it to reopen the business.

Permalink

A Five-Minute Internet Outage Is Not a Five-Minute Business Outage

An internet provider may correctly report that an outage lasted five minutes. The business may correctly feel that it lasted much longer.

Calls fail. Card payments pause. Staff lose access to web applications. Then the connection returns, and someone still has to find out whether the payment went through or whether the customer needs to try again.

Imagine a shop loses internet access at 10:00. The connection comes back at 10:05, but the cashier spends another seven minutes signing back in and checking which payments went through. For the shop, checkout took twelve minutes to recover. The provider’s outage report accounts for five of them.

NIST’s contingency planning guide makes a similar distinction between restoring a system and allowing enough time for the work that follows. A second internet connection may shorten the first part. It takes a separate check to know whether the work itself is back on track.

Pick one task you need to get back quickly, like taking a payment or answering a customer call. After a disruption, stop the clock when someone can do that task again and knows what happened to the work that was interrupted.

Permalink

Assorted Links — November 9, 2026

Permalink

Assorted Links — November 7, 2026

Permalink

A Grant Allocation Is Not a Resilience Project

On October 20, the U.S. Department of Energy announced about $967 million in additional Grid Resilience State and Tribal Formula Grant funding. For a community or organization interested in a local improvement, the next question is narrower than the headline: which part of a proposed project could this program actually fund?

The money goes to states, territories and federally recognized Indian tribes, which select eligible implementing entities through their allocation processes. An announced allocation is not an award to a particular town, business or utility. Nor does a useful infrastructure proposal become eligible simply because someone describes it as resilient.

One proposal, two funding scopes

Consider a hypothetical utility proposing to bury a vulnerable stretch of overhead line. Its long-term plan covers an entire route, but the available subaward would cover only one segment. The utility wants to present that segment as the first phase of the larger effort.

DOE’s October 28 FAQ makes the boundary consequential. Section V.5 says the federally funded portion should deliver a grid benefit on its own, without depending on other separately funded projects succeeding. The recipient must distinguish that portion from the broader project.

In our example, drawing a line around the affordable segment is only the start. Suppose its proposed benefit depends on completing another segment next year. If that later work has no committed funding, the first segment’s promised result rests on a project outside the subaward. Calling the first segment a phase does not resolve that dependency.

Now consider a different scope within the same hypothetical route: a segment whose undergrounding would address a specific exposure even if the rest stayed overhead. That proposal has a different funding argument. Its benefit can be explained separately from the aspiration to finish the route. This is a comparison of proposal logic, not an engineering finding that either segment would qualify.

The distinction could change which segment the utility proposes, how it describes the work, and what it seeks from other funding sources. It could also reveal that no useful independent segment exists. In that case, the team has discovered a financing problem before presenting a partial project as a complete resilience improvement.

Equipment labels do not settle eligibility

The same discipline matters when a proposal involves backup power. FAQ V.1 and V.4 expressly allow emergency backup combustion-based generation and specified outage-response storage. That does not make every generator or battery project eligible. Confirm the entity, technology and scope against the applicable award with the recipient and Federal Project Officer.

A facility may have several sensible continuity investments in mind: power equipment, controls, communications and staffing arrangements. Those are general planning possibilities, not a list of activities this grant will pay for. The proposal needs to separate the desired facility outcome from the particular work submitted for funding. Otherwise a persuasive description of the whole improvement can conceal an unsupported assumption about one component.

The recipient’s next step also depends on its history

A new applicant and an existing recipient do not necessarily repeat the same process. Under FAQ I.5, an existing recipient needs a revised narrative and associated notice and hearing when its implementation approach changed or its prior narrative did not contemplate projects beyond the earlier funding years. A new allocation alone does not automatically require another hearing.

For the hypothetical utility, that means the conversation with the sponsoring recipient should address both the proposed segment and the allocation process that applies now. A national announcement cannot answer either question for the local proposal. Nothing in this example establishes a Michigan award, a selected project or a local operating result.

The useful decision is whether to propose a fundable segment with an independent benefit, secure the missing support for a larger undertaking, or reconsider the scope. That is a more consequential choice than treating the size of the national allocation as the size of the local opportunity.

Permalink

How the 2026 Midterms Could Change IT Planning

AP projects Democratic control of both chambers, according to Axios. For IT professionals preparing next year’s budgets, that raises immediate questions about AI rules, data-center capacity and federal cybersecurity support. The practical impact will arrive on different schedules.

A congressional majority can change which proposals advance and which agencies face scrutiny. It cannot, by itself, turn a campaign position into an effective regulation or change the terms of a cloud contract. The incoming Congress begins in January 2027. IT planning needs to connect each political development to the particular decision it could affect.

AI policy: expect a different negotiation

The White House’s March 2026 national AI legislative framework already asks Congress to act on issues including children’s protection, AI-enabled scams and data-center permitting. It is a legislative framework, rather than a law enacted by its announcement. The election changes the political setting in which those requests will be considered.

Our assessment is that IT leaders should prepare for contested choices rather than assume either an immediate crackdown or a clear path to deregulation. A bill’s scope, the organizations it covers, implementation dates and eventual enforcement provisions will determine the work. An expectation of more oversight is not yet a requirement to run a particular algorithm audit.

Consider an organization deciding whether to embed an AI assistant in a customer workflow. It can distinguish commitments that are expensive to reverse from choices it can revisit. A contract that allows the provider to change data use, retention or model access deserves attention now because the organization must operate under that contract regardless of which proposal becomes law. A speculative compliance feature can remain a separately priced option until there is a defined requirement. This is a procurement approach, not a prediction about the final legislation.

Data centers: the project and jurisdiction matter

Texas shows why attributing every infrastructure constraint to the result would be misleading. On September 21, Governor Greg Abbott directed the Texas Commission on Environmental Quality, the state’s environmental regulator, to halt permits sought by data centers pending an audit by grid operator ERCOT. His announcement also required completion of ERCOT and Texas Water Development Board audits before permits could proceed. Those instructions came before the election.

Gina Hinojosa’s campaign separately called for a moratorium on data-center builds until the legislature could establish protections. That statement establishes her campaign position; it does not establish a new law taking effect on election night. The scope and implementation of any subsequent action will need to be checked in the actual government documents.

For an IT team, a proposed facility and an operating cloud region are different exposures. A migration that depends on capacity from an unfinished site may be sensitive to a permit or interconnection delay. An existing service is not shown to be unavailable merely because a politician proposes restrictions on new construction.

Suppose a supplier’s expansion is central to next year’s rollout. Ask which specific facility supports the commitment, what approvals remain outstanding and what capacity is available if the opening slips. The answer may change the rollout sequence or the contract negotiation. It does not justify assuming a national cloud shortage, a price increase or a service outage from the election alone.

Cybersecurity funding: follow the decision that changes the service

The administration’s fiscal 2027 budget proposes a $707 million reduction for the Cybersecurity and Infrastructure Security Agency (CISA). A presidential budget request is evidence of the administration’s priorities, not proof that Congress enacted that reduction. The election adds another variable to the funding debate; it does not tell a security team which specific assistance or information-sharing service will be available on a particular date.

Organizations that rely on federal or state assistance should follow the actual appropriation and the relevant agency’s service announcements. For example, a team whose incident plan depends on a government contact should confirm that contact and the supported response process directly. That is worthwhile preparation without asserting that federal intelligence has disappeared or that a particular staffing cut occurred.

The near-term effect of the midterms is a change in the decisions IT teams need to watch. Treat an enacted requirement as implementation work, a pending proposal as a scenario, and a supplier’s documented project constraint as a commercial dependency. Putting all three into the same urgent compliance bucket would obscure both the work that is required today and the choices still open.

Permalink

Post-Quantum Is an Inventory Problem Before It Is a Cryptography Problem

A post-quantum plan cannot begin with, “Which new algorithm should we buy?” It begins with a less glamorous question: where, exactly, does the organization rely on public-key cryptography, and which of those dependencies can actually be changed?

NIST’s new transition report is useful partly because it makes the answer larger than an encryption setting. The change can touch applications, cryptographic libraries, hardware, certificate infrastructure, network protocols, cloud services, and the vendors that maintain them. If those dependencies are unknown, a date on a roadmap is mostly decorative.

An inventory reveals the replacement problem

Consider a business with a customer portal, a VPN, laptops that verify software updates, a hosted line-of-business application, and a device that will remain in service for years. Each may use public-key cryptography differently. Some may be updated by a vendor. Some may need a firmware update, a new certificate process, or eventual replacement. Some may already use a service whose provider controls the underlying change.

That is why a useful first inventory is not a search for every mathematical detail. It is a record of the systems that protect important information or establish trust, what information must remain confidential for a long time, who supplies each system, and what the supplier says about its upgrade or replacement path. The record will be incomplete at first. That is still more actionable than treating the organization as one undifferentiated “encryption project.”

NIST IR 8547 describes the same practical layering: applications depend on libraries and hardware; public-key infrastructure has its own issuance, validation, and revocation work; protocols may need to accommodate different key sizes or interfaces. A change at one layer does not establish that the others are ready.

Not every item has the same clock

Post-quantum planning is often discussed as if a future quantum computer will ring a bell and every organization must migrate on the same afternoon. NIST does not describe it that way. Its federal timelines apply to particular federal systems, and the report says migration details and schedules vary by use case.

The difference matters. The “harvest now, decrypt later” risk is most relevant when someone can collect encrypted information today and that information must remain confidential far into the future. A short-lived transaction, a system that can be upgraded quickly, and a device with a long replacement cycle are not necessarily the same planning problem. Digital signatures, authentication, encrypted archives, and software-update verification also create different dependencies.

This is not an argument to wait for a prediction about when quantum computers will become capable enough to break current public-key systems. NIST says no such cryptanalytically relevant machine currently exists, while also noting that cryptographic migrations can take a long time. The sensible conclusion is narrower: identify which commitments last longest and which systems move slowest before deciding what should be first.

Ask suppliers for a path, not a promise

An inventory becomes useful when it produces specific conversations. For each consequential system, ask: What public-key functions does this product or service use? Who controls the upgrade? Is a supported post-quantum or hybrid option documented? Does a dependency such as a hardware module, certificate authority, remote peer, or older device limit the change? If the product cannot support the transition, is there a replacement or retirement path?

Those questions are not a demand for every vendor to deploy a new algorithm tomorrow. They are a way to discover where a future transition depends on contracts, refresh cycles, interoperability, or a decision someone else must make. NIST notes that systems unable to support post-quantum cryptography should be identified for replacement or decommissioning in the federal context; for other organizations, the comparable task is to know whether such a dependency exists before it becomes an urgent surprise.

Make the first deliverable small enough to use

A business does not need to turn this into a speculative technology program. Start with one bounded record: the service or system, the protected information or trust function, the owner and supplier, the expected life of the data or equipment, and the documented next step. Mark unknowns plainly. A supplier’s unsupported answer is useful evidence too.

That record will not choose an algorithm or prove that a migration is complete. It does something earlier and more valuable: it turns post-quantum cryptography from a distant noun into a list of business dependencies that can be scheduled, funded, or retired on purpose.

Permalink

Assorted Links — November 2, 2026

Permalink