Spend allocation
See how contract value distributes across tools, capabilities, and domains so you know where your security budget goes.
Last updated September 22, 2026
Spend allocation answers a question most security leaders struggle to answer cleanly: where does the money actually go? By distributing contract value across the tools and capabilities it funds, Pytheus turns a pile of invoices into a map of your security investment.
How allocation works
Allocation builds on the links you have already set up. A contract carries a value, resolved from its line items or its annual commitment. That value flows to the tools the contract funds, and because tools map to capabilities, the spend rolls up by capability and by CAMP domain.
The result is a view of cost that follows the same structure as the rest of Pytheus. You can see how much you spend supporting Identity and Access Management versus Endpoint and Device Security, or which single capability carries the heaviest cost.
For this to be accurate, two things need to be in place:
Contract values are recorded. See Uploading contracts.
Contracts are linked to the right tools, and tools are mapped to capabilities. A tool with no mapping stays unattributed.
Why it matters
Spend mapped to capabilities lets you weigh cost against importance. A compliance-required capability that draws heavy spend is money working hard. A nice-to-have capability with the same cost is a candidate for review.
Spend allocation describes where money goes. It does not change your scores. Maturity and priority come from CAMP, so high spend on a capability does not raise its maturity, and low spend does not lower it.
With spend mapped this way, you are ready to judge whether those numbers are reasonable against peers. See the Pytheus Index spend benchmarks.