New "End of Life" adoption level
Based on user feedback, we’re always improving the CYBER HEAT MAP assessment process.
We added the latest feature at the suggestion of one of our users. They suggested highlighting technology that had reached end-of-life and needed to be updated urgently.
Options to highlight deployed solutions that need updates
To help you more accurately track your capability deployment lifecycles, the CYBER HEAT MAP assessment now includes two adoption level options that count the capability as deployed when evaluating compliance readiness, but that add the capability into the mix when evaluating potential improvement projects.
- You should use the “Needs Refresh” adoption status means that the capability is in widespread use, but you need work done to improve the deployment, update how it’s configured, etc.
- You should use the new “End of Life” status for capabilities that are in widespread use despite the vendor no longer supporting the deployed technology.
Unsupported technology carries more risks, so this new status increases the relative urgency of the upgrade for end-of-life capabilities versus capabilities that just need a refresh.
Summary of capability adoption lifecycle
The CYBER HEAT MAP assessment now includes five stages for you to use when evaluating your adoption of each capability.
Not Adopted
This capability is not currently in production use. This includes deployments that are limited to test instances.
Partially Adopted
This capability is in limited production use, such as within individual departments or by a select group of users.
Widely Adopted
This capability is in widespread use and has been deployed to most departments and users.
Needs Refresh
This capability is in widespread use, but the deployed solution needs to be updated or enhanced.
End of Life
This capability is in widespread use, but the deployed solution has reached end of life and needs to be replaced.