An increasing security budget may be entirely justified as a business grows. It may also reflect years of renewals, overlapping subscriptions and products bought in response to individual concerns. The important question is not whether those products have useful features. It is whether the overall arrangement addresses a genuine business exposure and can be operated well enough to make a difference.
I would want every significant investment to have a reason that can be explained without starting with the product name. What is at risk, what is inadequate today and what evidence will show that the proposed change has helped?
Describe the decision before the purchase
A worthwhile proposal connects an essential service to a credible scenario, explains the current limitation and sets out the available options. It should also say what will remain unresolved after implementation.
“Improve monitoring” is too vague to test. A clearer requirement would be that suspicious access to the customer platform can be investigated and escalated within an agreed service window. That still leaves practical questions about which systems are covered, who examines the information and who can make a decision when the alert arrives.
The NCSC distinguishes logging—recording relevant activity—from monitoring, which examines that information for possible incidents [S9]. This is more than a technical distinction. Buying a way to collect information does not mean the business has acquired a service capable of investigating and responding to it.
A useful requirement should make sense even when the proposed supplier's product name is removed. If the concern is suspicious access to a customer platform, identify the accounts in scope, the hours of coverage, the route from alert to decision and the consequence of delay. The business can then compare an internal process, an external managed service or a further technical control against the same outcome. Feature comparisons are less meaningful while these fundamentals remain unclear. The important question is how the full arrangement works, not which option offers the longest list of capabilities.
Include the cost of operating the improvement
The licence is only one part of the cost. Implementation, integration, training, staff effort, supplier support and continuing administration all influence whether the arrangement is viable. A technically impressive option can still be unsuitable for a team that lacks the time or capability to use it.
Compare alternatives over the same period and against the same requirement. Include migration, testing and eventual exit where relevant. Sometimes a modest change to an existing process is a sensible interim step while a larger improvement is developed. That choice still needs an explanation of what it protects, where it falls short and how long it will remain appropriate.
Financial estimates also need care. Assigning a precise return to an uncertain incident probability can create more confidence than the evidence deserves. Where a financial range is helpful, show the assumptions. Revenue delayed is not always revenue lost; some work can be recovered while some transactions disappear altogether. Backlogs, customer disruption and later consequences should not be ignored just because they are harder to calculate.
Security operations consume attention. An alert needs someone, or a dependable defined process, to decide whether it matters and what should happen. Without that capacity, an advanced monitoring platform can create a growing queue of unresolved issues. Ongoing costs should also include specialist support, integration changes and the ability to leave the supplier. Are logs and configurations retrievable? Can the service be operated if the original implementer leaves? A smaller, properly supported capability can be more effective than a broad one that the business has no realistic capacity to run.
Use measures that support decisions
Activity has a place in reporting, but it is not the same as effectiveness. Training attendance tells the business that people completed a course; it does not show whether they can easily report a concern or whether an important report receives a response. Software update numbers need to be understood alongside exceptions affecting important services.
Recovery reporting should be just as specific. “Test complete” tells very little. A useful record identifies the service, the circumstances, elapsed time, information restored and business checks performed. One successful exercise should not be presented as proof of recovery for systems that were never in scope.
Percentages need a clear denominator too. An account protection figure loses much of its meaning if privileged users, newly acquired systems or unmanaged accounts have been excluded. A smaller measure with well-understood coverage may provide a much stronger basis for decisions than an impressive overall percentage.
I would organise reporting around three questions: is the intended scope covered, does the process actually operate as agreed and what has the latest evidence shown? Percentages can be useful but require context. Ninety-nine protected accounts may sound excellent until the missing one is a shared administrative identity. A recovery success rate says little about an essential service that has not been tested. Measures therefore need visible denominators, exclusions and decision thresholds. The purpose of the report is to show what needs attention, not to generate a single reassuring figure.
Revisit the original reason for spending
Imagine a business that contracts for managed detection because its own team cannot provide overnight coverage. At renewal, I would return to that requirement. Are the agreed systems monitored? Does the escalation route work? Can somebody with the right authority respond during the hours that matter?
The volume of alerts processed may help explain the service, but it does not answer those questions by itself. If the expected outcome has not been achieved, examine why. The problem may lie in configuration, deployment, responsibilities or the contract. More spending is one possible response; correcting the service or removing duplication may be more appropriate.
Renewal should return to the business requirement. What outcome was expected, what has been demonstrated and what has changed since the decision? If an overnight detection service still cannot reliably reach an authorised decision-maker, the first remedy may be a clearer escalation agreement rather than a more expensive product. Equally, a service that once met the need may no longer be sufficient after the business adds a critical application or expands its operating hours. The answer could be to retain, adapt, replace or discontinue the arrangement; it should follow the evidence rather than inertia.
Sources and further reading
[S9] NCSC. 10 Steps to Cyber Security Logging and monitoring. Read original guidance
[S1] UK Government. Cyber Governance Code of Practice. Read original guidance
The source collection records these references as checked on 28 October 2026. Source attribution does not imply endorsement.
Scenarios are illustrative, not client case studies. This article provides general business guidance, not a security audit, certification or substitute for sector-specific technical, legal or contractual advice.
