exploitation code
set file system permissions preventing exploitation code from
being written to disk
white and blacklisting to prevent code execution
controls to detect attacks including:
deploy an IDS
monitor logging alerts
use other mechanisms as appropriate for the detection of
exploits using the known vulnerability
controls to prevent attacks including:
deploy an IPS or HIPS
Recommended Control 3:
use other mechanisms as appropriate for the diversion of
exploits using the known vulnerability, such as honey pots
and null routers.
Agencies should assess the security risk of using software or IT
equipment when a cessation date for support is announced or when
the product is no longer supported by the developer
It is important that agencies monitor relevant sources for information about new vulnerabilities and
security patches. This way, agencies can take pro‐active steps to address vulnerabilities in their
systems.
When a security patch is not available for a known vulnerability, there are a number of approaches
to reducing the risk to a system. This includes resolving the vulnerability through alternative means,
preventing exploitation of the vulnerability, containing the exploit or implementing measures to
detect attacks attempting to exploit the vulnerability.
As firmware provides the underlying functionality for hardware it is essential that the integrity of
any firmware images or updates are maintained.
Once a cessation date for support is announced for software or IT equipment, agencies will
increasingly find it difficult to protect against vulnerabilities found in the software or IT equipment
as no security patches will be made available by the manufacturer. Once a cessation date for
support is announced agencies should investigate new solutions that will be appropriately
supported and establish a plan to implement the new solution.
64
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents