Security budgets face constant scrutiny, but adding technology is only one way to reduce risk. What if an organization could improve security without increasing its budget?
Many enterprises already possess significant security capabilities that are:
- Inconsistently deployed.
- Poorly configured.
- Undermined by excessive access.
- Weakened by exceptions.
- Not routinely tested.
Building on Cybersecurity Awareness Month, organizations can conduct a "$0 initiative" consisting of a one-week diagnostic and remediation exercise. Although no new technology purchases are required, organizations should plan for the necessary labor and operational effort.
This activity answers the executive question, "Do we have a capability gap or an execution gap?"
The seven-day, zero-dollar security checklist
This weeklong executive checklist prompts CISOs and their teams to verify specific operational procedures, provide practical information, remove potential risks and confirm processes.
Day 1. Enforce MFA on high-value access
MFA adds a critical layer of security, but gaps in password management can undermine its effectiveness. Without additional spending, teams can:
- Verify MFA coverage for privileged accounts, remote access, administrative interfaces and externally accessible applications.
- Identify exceptions and require documented ownership and justification.
Day 2. Remove excessive and dormant access
While reviewing MFA for privileged accounts, search for orphaned, duplicate or dormant accounts that might provide unmanaged access to resources. Determine who currently has access that they no longer need, and who owns the decision to remove it.
- Review privileged accounts and standing administrative access.
- Remove or disable unused employee, contractor, service and application accounts.
- Identify and investigate orphaned accounts without clear owners.
- Verify whether third-party or vendor access remains necessary.
- Identify access provisioned as part of acquisitions, reorganizations or contractor engagements.
Be sure to validate dependencies and identify ownership before removing access. When in doubt, disable accounts rather than deleting them.
Day 3. Reduce unnecessary attack surfaces
Examine the existing attack surface and identify opportunities to trim it.
- Identify internet-exposed systems, unnecessary services, unused interfaces and legacy protocols.
- Review security configurations for permissive settings and configuration drift.
- Disable unnecessary services only after testing for dependencies.
- Distinguish legitimate business exceptions from forgotten exposure.
The goal is to identify externally reachable but unnecessary systems and services.
Day 4. Review security exceptions and compensating controls
As the adage goes, there's an exception to every rule. Document all exceptions to security policies or standard configurations so they can be tracked and periodically evaluated. Include the following information for each exception:
- Business owner.
- Expiration or review date.
- Documented risk acceptance.
- Effective compensating controls.
Undocumented and unreviewed temporary exceptions introduce an invisible risk.
Day 5. Verify backups and prove recovery
Backups are only as good as the recovery processes behind them, and backup tools only protect what they cover. As storage requirements and locations change, ensure backups target all necessary resources.
- Confirm backup programs actually back up critical systems and data.
- Review backup access control and isolation.
- Ask when the most important systems were last successfully restored.
- Distinguish backup completion from recoverability.
- Identify recovery dependencies that could prevent restoration during an incident.
Day 6. Document the recovery path
Documentation is a key component of resilience, compliance and security. Add documentation verification to this initiative. Focus on practical recovery steps rather than documentation for its own sake. Specifically:
- Confirm the accuracy of incident response, escalation, recovery and ownership data.
- Identify who can authorize critical decisions during an incident.
- Ensure recovery documentation remains usable if normal systems are unavailable.
Day 7. Establish evidence of control effectiveness
Capture simple evidence for every completed task or remediation on this list to enable auditability and show due diligence. Answer the following questions:
- What changed?
- Who owns it?
- How was it validated?
- What exposure was reduced?
- What exceptions remain?
Documenting this information prevents the exercise from becoming a collection of "tasks completed" without evidence that security actually improved.
Decide what to fix, govern or buy
Not every security problem can — or should — be addressed without spending. By establishing a decision-making framework, however, IT leaders can determine whether existing systems and controls can remediate specific challenges.
Fix what existing capabilities can address
Prioritize zero-cost changes that:
- Use existing technologies.
- Address meaningful exposure.
- Have identifiable owners.
- Can be validated.
- Present manageable operational risk.
Starting with these items enables the organization to quickly eliminate material risks and reduce the attack surface without increasing spending.
Govern what is fundamentally an ownership problem
One crucial objective of this exercise is to identify risks, accounts, systems and other potential vulnerabilities that don't currently have owners. Without owners, decisions go unmade, systems go unmanaged and security gaps widen. Collect and address:
- Undocumented security exceptions.
- Unclear account ownership.
- Inconsistent policy enforcement.
- Missing recovery responsibilities.
- Third-party access without accountable owners.
Buy when there is a genuine capability gap
Not all risks can be addressed through identification, reconfiguration and documentation alone. The $0 initiative isn't an excuse to defer necessary investments; it's a way to ensure those investments are planned better and implemented more effectively. The goal is to answer the question, "Is the organization missing a capability or is it failing to use one it already has?"
Turn the exercise into better security investment decisions
This one-week, zero-cost exercise can become an ongoing governance and future-spending program that ensures existing investments deliver their intended security outcomes while achieving the best ROI possible. Use the results to distinguish:
- Correctable exposure using existing tools.
- Ownership and governance problems where decisions go unmade.
- Genuine technology gaps where investment will matter most.
For each product, workflow, third-party access point or security exception, leadership should require:
- Accountable owners.
- Measurable remediation.
- Evidence of completion.
- Documentation and review periods.
Ask the security and infrastructure leadership team to identify a short list of existing controls to strengthen within one week, and require them to return with evidence of what has changed and what actually requires investment.
Damon Garn owns Cogspinner Coaction and provides freelance IT writing and editing services. He has written multiple CompTIA study guides, including the Linux+, Cloud Essentials+ and Server+ guides, and contributes extensively to Informa TechTarget, The New Stack and CompTIA Blogs.