CompTIA Network+ (V9)
Asset inventory, baselines and end-of-support for Network+
An asset inventory lists every component once, with a unique identifier, model, serial number, software version and network addresses. A baseline configuration is a formally reviewed and agreed specification that changes only through change control. When the vendor stops supporting a device, NIST SP 800-53 says replace it or arrange other support, with narrow exceptions.
What the asset inventory holds
NIST SP 800-53 Rev. 5 control CM-8 calls this the system component inventory. It must reflect the system accurately, include every component, and not count any component twice.
The control's discussion lists the information needed for accountability: system name, software owners, software version numbers, hardware specifications, license information and, for networked components, machine names and network addresses. Hardware specifications include date of receipt, cost, model, serial number, manufacturer, supplier, component type and physical location.
Preventing duplicate accounting needs a unique identifier for each component. Model and supplier are shared by many units, so they cannot do that job.
Example: a vendor advisory names certain firmware builds of a switch model. With software versions in the inventory, you can list the affected switches without logging in to each one.
Baseline configuration and change control
Control CM-2 describes baseline configurations as documented, formally reviewed and agreed-upon specifications. They serve as a basis for future builds, releases or changes, and include information about components, network topology and the logical placement of components.
The NIST glossary adds that a baseline can be changed only through change control procedures. CM-2 also requires the baseline to be reviewed and updated when components are installed or upgraded.
A running configuration that no longer matches the baseline, with no change request behind it, is therefore an unauthorized change to investigate.
Unsupported components
Control SA-22 says support includes software patches, firmware updates, replacement parts and maintenance contracts from the developer, vendor or manufacturer.
When that support ends, the control says to replace the component, or to provide alternative support in-house or from external providers under contract.
SA-22 names exceptions: systems providing critical capabilities where newer technologies are not available, or systems so isolated that replacement is not an option. It suggests reducing the risk of keeping such components, for example by not connecting them to public or uncontrolled networks.
Where the exam catches people
- Believing a model number identifies one unit: many units share it; CM-8 calls for a unique identifier per component.
- Believing a baseline is just the current running configuration: it is a formally agreed specification that changes only through change control.
- Believing unofficial community fixes count as continued support: SA-22 means vendor support, or in-house or contracted alternatives.
- Believing unsupported gear must always be removed at once: SA-22 allows exceptions for critical or isolated systems with no newer option.