Finite People, Finite Time, Infinite Threat
Why manual STIG compliance work is always the first thing a stretched cyber team drops.
By Ar-Raheem Ellis, Senior Program Manager of Strategic Accounts, SteelCloud. 25.5 years in Navy cybersecurity and IT, ending as an Operations Branch Chief of the Fleet Cyber Command Office of Compliance and Assessments.
Whether you are operating from an offensive or a defensive cyber mission perspective, the sustainment challenges facing Department of War cyber teams are numerous and often interconnected. Pull on one and three others move.
One of the most significant is resource management, which encompasses several critical areas: personnel management, technology management, and time management. I would argue that the third one is the least discussed and the most decisive.
The Policy Is Not the Problem
The DoW invests considerable effort in developing policies, instructions, and force management requirements designed to ensure cyber units are properly staffed, trained, and equipped to execute their missions. These frameworks establish clear expectations for manpower, readiness, training, and capability development across the services.
I want to be direct about this, because it is easy to write about DoW cyber challenges as though the guidance were absent. It is not. The expectations are documented, and they are reasonable. The gap is not between what the policy says and what it should say. The gap is between what the policy expects and what a given command can actually resource on a given day.
Where the Constraints Actually Bind
Despite those efforts, cyber organizations routinely encounter resource constraints that impact operational effectiveness:
- Personnel shortages
- Retention challenges
- Training requirements
- Rapidly evolving technologies
- Competing mission priorities
- Limited time available for sustainment activities
Every one of those contributes to readiness gaps, and they compound. A personnel shortage increases the workload on the people who remain, which reduces the time available for training, which slows the development of the capability that would have relieved the shortage.
As a result, cyber teams are often required to balance mission execution with the continuous development and maintenance of the people, processes, and technologies necessary to remain effective in a constantly evolving threat environment. That balance is not struck once. It is struck every week, usually by a mid-level leader deciding which necessary thing does not get done this week.
Sustainment Activities Are the First to Slip

When something has to give and often times it is the sustainment work. Baseline reviews, documentation updates, training, configuration audits, the unglamorous maintenance that keeps a security posture from decaying. None of it has a customer waiting on it today, which is exactly why it slides.
And sliding is invisible for a while. That is the dangerous part. A team can defer sustainment for a month and see no consequence, defer it for a quarter and see no consequence, and then discover the cost all at once, usually during an assessment or, worse, during an incident.
What This Requires of Cyber Leaders
While policies and guidance provide the foundation for readiness, the practical realities of managing finite resources continue to present challenges for cyber leaders at every level. Successfully addressing these challenges requires more than compliance with established requirements. It demands continuous prioritization, adaptability, and strategic investment to sustain operational readiness over the long term.
Continuous prioritization means accepting that the list will never be finished and deciding, deliberately and repeatedly, what matters most right now. Adaptability means the plan you built in January will not survive contact with June. Strategic investment means putting resources into things that reduce future workload rather than only into things that address today’s findings.
That last one is where automation enters the conversation, and it is where I will spend a full post later in this series. Before that, though, I want to talk about the single most common way I have seen a technically sound environment quietly become unsafe. It has nothing to do with a missing tool.
READ THE ENTIRE SERIES
Enjoyed “Finite Time, Finite People, Infinite Threat”? Click on the links below to read other blogs in this series written by Ar-Raheem Ellis.
Blog #1: Compliance Status is Not a Readiness Report
Blog #2: The Dopamine of Passing the Audit