Assorted Links — October 30, 2026
No name or email needed. Select a rating to add details; click it again to clear it.
CTS Field Notes
Practical technology judgment for business leaders. Fresh perspectives for curious minds.
No name or email needed. Select a rating to add details; click it again to clear it.
Imagine a future managed-IT proposal that does not sell a block of technician time or a ticket queue. It promises something narrower and more useful: a new employee can work, a routine access problem is resolved, a known security event is contained, and the business can see whether those things actually happened. That is a hypothetical purchase, not a description of a CTS service or a claim that such a complete product is available today.
Pieces of that proposition already exist. The harder question is whether the pieces amount to an IT department that can be bought as software—or whether they only make a human-run service desk more efficient.
Some current tools take action across the systems behind a common employee request. Moveworks, for example, describes workflows spanning service management, identity, endpoint management and monitoring for actions such as password resets and VPN troubleshooting. That is more than a chatbot finding an article. But it is vendor documentation, not an independent measure of what happens across every application, device and unusual request at a 25-person company.
The useful unit of work is also larger than the request. “I cannot connect to the VPN” may involve the account, device posture, network path, remote-access service and a change made earlier in the day. Resolving it means restoring the employee’s ability to do their work without opening an unsafe path or obscuring the cause. A system that closes the ticket quickly but leaves the user unable to reach a critical application has completed an administrative event, not the business outcome.
That distinction is why automated validation matters. HPE’s Marvis Minis documentation describes synthetic wired and wireless client checks that test items such as DHCP, DNS, authentication and application reachability even when no user is present. Its documented scope depends on specified network equipment, software versions and subscriptions. Still, the idea is important: an operating service needs evidence that a service works, not merely evidence that a command was sent.
In a hypothetical purchase, the provider could make an outcome claim concrete: after a change, show that the designated user path works; after a network alert, show which expected path was tested and what was not. That would give a buyer something more useful than a dashboard saying that an automation ran.
Automation does not remove the question of who is allowed to act. NIST’s zero-trust architecture separates authentication from authorization: proving who or what is making a request does not by itself establish permission for that request. An agent that can change passwords, install software or modify access needs bounded authority just as an employee does.
The same is true when an automated security control acts quickly. Microsoft Defender for Business documents automatic containment of devices and user connections after it detects certain advanced attacks, while leaving investigation and release actions for authorized administrators. That is a useful division of labor, not evidence that a customer can dispense with review, recovery decisions or accountable ownership.
For a buyer, the practical questions are specific. Which actions can the service take without asking? Which action requires a named approver? What evidence shows that the action worked? Who can reverse it, and how does the service operate if its own control plane or an integration is unavailable? Those questions do not assume that humans are permanently indispensable. They define the evidence needed to compare a software-operated service with a people-operated one.
An IT service could become increasingly software-like without becoming universally autonomous. The relevant commercial test is not whether a demo resolves a password reset. It is whether a provider can state the supported outcomes, show the systems and permissions required, measure success across normal work, and price the exceptions honestly.
If independent evidence eventually shows that a product can deliver those outcomes across a representative business environment at lower total cost and with manageable exception work, “we need a provider because IT requires people” will be a weak reason to reject it. Until then, a buyer does not need a prediction about the end of managed services. They need a proposal that makes its operating promises observable.
No name or email needed. Select a rating to add details; click it again to clear it.
Before signing off on an office move, ask the phone provider what location an emergency call from the new office will report. A successful call to a customer answers a different question.
For a business using internet-based phone service, the move includes an emergency-location task. The National 911 Program advises owners to contact their VoIP provider when moving a phone so its physical location can be updated. A familiar number and a working internet connection should not be treated as confirmation that this has happened.
Consider a hypothetical company moving from one leased office to another. It keeps its telephone numbers. Staff can receive calls at the new desks and call customers. Those checks are useful: the business needs ordinary calling to work on opening morning.
Now give the move coordinator one additional acceptance question: what emergency location is associated with the phones at those desks? The answer might already be correct. It might require a provider update, a change by the phone-system administrator, or confirmation that automatic location detection recognizes the new network. The point of the question is to find out which applies before declaring the move finished.
This is a recommendation for organizing the handoff, not an account of a CTS customer move. The coordinator does not need to configure emergency calling personally. They need the responsible provider or administrator to explain how the installed service identifies location and what has been checked at the new premises.
Some systems can determine an emergency location from the network a device connects to. Microsoft’s Teams documentation describes a service that matches a client’s network information against an administrator-defined map of emergency locations. That map can use Wi-Fi access points, switches or subnets.
This is an important qualification to the simple advice to update an address. An organization may have dynamic emergency calling rather than a single address that stays attached to a phone. The check should fit the actual system. For Teams, the documented mechanism depends on configured network and location information; automatic detection is not evidence that every new office has already been mapped.
Microsoft also documents emergency-address management separately from assigning locations to users. It notes that management and requirements vary with the phone connection option. That makes a useful distinction for the handoff: having the new address in an administration screen is one fact; establishing how the relevant users or devices obtain that location is another.
For the hypothetical move, ask for an explanation tied to the new premises and the ways people will call there. If staff use both desk phones and a laptop calling app, include both in that conversation. Do not assume that checking one device establishes the behavior of every other device or work location.
A sensible move record would identify the premises, the calling arrangements checked, who confirmed the emergency-location setup, and anything still unresolved. This is our proposed acceptance record, not a universal technical procedure or proof of legal compliance. Keep the provider’s instructions with it rather than inventing a test from a generic checklist.
The National 911 Program says a test call can confirm reception and location information, but it should be arranged through the local 911 center’s non-emergency number. Contact the provider about its supported checks and coordinate any emergency-service test in advance. Do not dial 911 just to obtain that non-emergency number or make an unarranged test.
Then close the office-move task with a specific result: the emergency location for the new premises has been confirmed through the applicable process, or a named part of that confirmation remains outstanding. That gives the person accepting the move something more useful than “the phones work.”
No name or email needed. Select a rating to add details; click it again to clear it.
NIST’s Small Business Cybersecurity Support Program Finder connects small businesses with nonprofit programs offering cybersecurity assistance. Its October 5 announcement describes support ranging from risk assessments to incident preparedness. You can browse programs by state.
A useful first conversation begins with what you want help understanding. For example: which accounts can approve payments, or whom should we call if our email is compromised? These are illustrative questions, not reports of incidents. They give a prospective provider a specific problem to discuss.
If you cannot yet name that problem, ask for help finding the starting point. NIST’s team-building guidance specifically allows for community support to help identify major risks and areas for improvement, particularly for businesses with limited resources, relatively simple IT, and no significant external cybersecurity requirements.
Then ask what the provider would examine, what your business would receive, and what you would know afterward. In the payment example, would the work identify relevant accounts and approval steps? In the email example, would it produce a contact plan that staff can find and use?
NIST says the finder’s list is not exhaustive and does not endorse or validate the listed programs. Its team-building guidance also recommends defining desired outcomes and documenting service responsibilities. Use the first conversation to establish whether the offered help fits your situation and what work, if any, should follow.
No name or email needed. Select a rating to add details; click it again to clear it.
No name or email needed. Select a rating to add details; click it again to clear it.
Attackers changed passwords and network addresses on computers used to monitor and control water systems. Utilities lost monitoring or control, and reported effects included pressure loss and flooding, according to a July 30, 2026 FBI/EPA warning. For some affected controllers, restoring access poses another problem: the recovery procedure erases the program that runs the equipment.
The agencies’ announcement covered incidents reported since July 27 by utilities in at least seven states. That is the July account, not an updated victim count. Rockwell’s recovery guidance, updated September 18, explains what restoring access requires for particular controller models. It does not tell us which procedure any individual utility used or how long its recovery took.
A controller is a small industrial computer assigned to monitor equipment, control it, or both. Losing access can therefore have different consequences: operators may lose their view of a process, the ability to control equipment, or both. The FBI says the effect depended on the controller’s job and the facility’s ability to switch to manual operation.
Rockwell’s guidance addresses controllers whose passwords are unknown. For the models it covers, recovering access involves clearing the stored program and loading a retained project file. The manufacturer warns that an offline copy is needed before the reset. Once the program has been erased, the controller cannot provide the missing copy.
That creates two separate recovery tasks: regain access to the device and restore the instructions it should execute. A successful reset can complete the first task while leaving the second unfinished. The useful question about a backup is therefore whether it contains the program appropriate for the equipment now in service.
An old file may predate a legitimate change. A more recent copy could contain an unauthorized one. Those are possibilities to check, not findings about any particular utility. The FBI recommends reviewing controller project files against known-good logic and checking backups for malicious changes before deployment. A filename and a recent date cannot establish what the program will do.
There is also a physical requirement that routine remote maintenance can leave untested. For the MicroLogix 1100, one of the controller models identified in the July warning, Rockwell specifies a serial connection for the recovery operation. That means having the appropriate cable and a compatible computer connection available. The procedure does not support Ethernet, the usual wired network connection.
This limitation belongs to that model’s documented recovery route; it is not a rule for every industrial controller. Its practical significance is straightforward: being able to reach a device over the network does not establish that the same equipment can recover it after a lockout. The qualified integrator needs to identify the applicable software, connection hardware and local access requirements for the installed model.
These are preparation checks, not instructions to reset a live process. A restoration demonstration belongs in a separately authorized, safe test arrangement. The manufacturer’s notice provides recovery and hardening guidance; it does not identify a newly disclosed software vulnerability.
The agencies also recommend practicing manual operation. That serves a different purpose from blocking an intruder: it can provide a way to continue an essential process while normal monitoring or control is unavailable. Whether it is workable depends on the equipment and the people operating it. A written fallback should not be mistaken for a demonstrated capability.
For an organization that depends on a controller, a useful preparation check starts with one function: establish how it could operate safely during a control outage, locate and verify the retained program, and confirm that the appropriate recovery tools and authorized site access are available. This is our recommendation drawn from the documented dependencies, not a reconstruction of a utility’s response or a report of CTS testing.
The check should leave any missing prerequisite plainly identified. The available records may establish that a backup exists while leaving its contents unverified, or identify the correct connection while leaving the necessary hardware unavailable. Those are specific problems that can be resolved before access to the controller is lost.
No name or email needed. Select a rating to add details; click it again to clear it.
An approved application presents valid credentials to a network controller, then asks for information it has no reason to use. That is a hypothetical threat scenario in NIST’s O-RAN security report: code added to an otherwise approved app could collect and export information outside its normal work. The credentials could still check out. NIST describes a possible attack, not a reported incident.
The distinction is useful when evaluating an application for a controller. Establishing which app sent a request leaves another decision: whether that app should be able to make that particular request. A product demonstration may show the useful result while leaving the extent of the access difficult to see.
When a controller accepts third-party applications, the buying conversation needs to reach the permissions of each application. Which information may it read? Which commands may it issue? How closely do those capabilities match the job it was installed to perform?
The report concerns the RAN Intelligent Controller in Open Radio Access Networks, a mobile-network architecture. It describes specialized applications that obtain information or influence network operation through the controller. Section 2, printed page 6, separates a request from an impersonator from an unnecessary request made by an approved component. That second possibility supplies the example above.
The enterprise comparison here is narrower than the telecom architecture: examine the authority attached to an application. Consider the following illustrative building-control purchase. An organization wants a weekly report identifying rooms whose temperatures fall outside a chosen range. The proposed reporting app reads measurements and produces that report. Changing the building’s operating schedule would be a separate capability.
For this example, the first permission review can stay close to those two actions. The buyer asks the integrator to identify the measurements the report consumes and to show whether the app can also submit schedule changes. If the integration requires a broad service account, the proposal should explain which additional actions that account permits and why they are needed.
An app that reads measurements can expose the information it receives. An app that changes a schedule can affect when equipment operates. In our hypothetical purchase, allowing both would enlarge the app’s authority beyond the stated reporting task. The organization could choose a narrower integration, accept a documented limitation, or decide that a different feature justifies additional access.
Those are decisions about a specific capability. A general statement that the application is trusted or comes from an approved supplier leaves them unanswered. The useful evidence would connect the requested permission to a named function: this information is needed to calculate the weekly report; this command is needed only if automated schedule adjustment is purchased.
The distinction also makes a demonstration more informative. In a safe test environment agreed with the integrator, the organization could ask to see the reporting workflow succeed and an out-of-scope schedule-change request refused. A screenshot of the finished report establishes the output. The second observation tests the proposed access boundary.
Suppose the organization later adds automatic schedule adjustment. In this illustrative extension, the app’s job has changed, so write access may now have a purpose. The decision needs to specify the schedules it may alter, the conditions under which it may act, and how an operator can restore an acceptable setting. Keeping the earlier reporting-only description would conceal that expansion.
If the platform cannot separate those permissions, that constraint belongs in the purchase decision. The buyer may need an additional control, a restricted deployment, or a different integration. A demonstration can then end with a concrete record: the app can read these measurements, issue these commands, and is blocked from these other actions. Any capability the test could not establish remains an open item.
Source: NIST IR 8625, section 2, printed page 6; NIST publication record and report scope.
No name or email needed. Select a rating to add details; click it again to clear it.
No name or email needed. Select a rating to add details; click it again to clear it.