CIS-1355 · Security Engineering · Module 15

Information Security Management

Track assets throughout their lifecycle, manage changes, and make risk decisions that others can verify.

Manage assets from acquisition to retirement

An asset supports an organizational objective or has value to the organization. Assets include equipment, software, cloud resources, data, and services. Cybersecurity asset management (CAM) links inventory to security information such as exposure, support status, and missing controls. Reconcile discovery results with inventory records regularly.

  1. Acquire. Document the business purpose, security requirements, support period, and license terms before procurement or provisioning.
  2. Assign and track. Record the asset ID, owner, location or cloud account, classification, and dependencies. Update the record when the asset moves or changes hands.
  3. Retire. Confirm retention and legal-hold requirements. Revoke access, recover or securely dispose of equipment, deprovision virtual resources, and update the inventory. Record what happened to associated data and media.

Deleting a file ordinarily leaves data potentially recoverable. Choose a sanitization method based on the media, data sensitivity, and intended reuse. NIST describes three methods. Clear addresses recovery through ordinary interfaces. Purge uses stronger techniques against advanced recovery and can allow reuse. Destroy makes the media unusable. Overwriting can be suitable for some magnetic media. Flash storage can retain data outside the normally addressable area, so use a validated method suited to the device. Degaussing applies to suitable magnetic media. Sensitive paper can be handled through an approved shredding, pulping, or destruction service. Verify the outcome and record disposition.

NIST SP 800-88 Rev. 2 · Guidelines for Media Sanitization

Make changes traceable and reversible where practical

Change management coordinates updates to systems, services, and work processes. A policy defines which changes need review and approval, who can authorize them, and how emergency changes are handled. A ticketing system, configuration repository, or deployment pipeline can preserve the change record.

Document the purpose, affected systems, security and service impacts, tests, maintenance window, and rollback plan. Obtain the required approvals, notify affected teams, implement the change, and verify the result. Update asset and configuration records. For urgent changes, document the reason and complete any retrospective review required by policy.

NIST · Security-Focused Configuration Management

Identify, estimate, and report risk

Describe a risk as a scenario connecting an asset, a threat or failure, weaknesses or conditions, and a consequence. Examples include internal misconfiguration, external attacks, unsupported legacy systems, outages at connected suppliers, and software licensing violations. A risk and control self-assessment (RCSA) brings staff and managers together to identify risks and evaluate controls. Use incident records, inventory data, and feedback across teams to challenge assumptions and reduce blind spots.

Qualitative assessment uses defined likelihood and impact categories. A risk matrix or heatmap shows how the categories combine. Quantitative assessment uses numerical estimates, such as frequency and financial loss. Both depend on the quality of the evidence and assumptions. Use ranges where a point estimate would imply more certainty than the evidence supports.

Reliability and recovery
Mean time between failures (MTBF) describes time between failures for repairable equipment. Mean time to failure (MTTF) is often used for nonrepairable components. Failures in time (FIT) expresses expected failures per billion device-hours. MTTR can mean mean time to repair or recover, so define it in the report. These operational measures inform relevant risk scenarios.
Annualized loss
The annualized rate of occurrence (ARO) estimates events per year. In a simple model, single loss expectancy (SLE) equals asset value multiplied by the exposure factor, the fraction of value lost per event. Annualized loss expectancy (ALE) equals SLE multiplied by ARO. Treat the result as an estimate of expected annual loss.

A risk register records the scenario, affected assets, likelihood, impact, response, risk owner, due date, and residual risk. A key risk indicator can track changes in exposure, such as the number of unsupported systems still reachable from partner networks. A threshold can trigger an escalation or review. The risk owner is accountable for managing or escalating the risk and may differ from the asset owner.

NIST · Identifying and Estimating Cybersecurity Risk

Choose a response and build risk awareness

Risk appetite describes the types and amount of risk the organization is willing to take in pursuing objectives. Risk tolerance sets more specific boundaries, such as the maximum exposure or downtime allowed for a service. Check the residual risk after a response against those boundaries.

For third parties, assess what they can access and which services depend on them. Contracts and interconnection agreements can define responsibilities for incident notification, access, evidence of compliance, and exit or data return. Review performance and reassess after significant changes.

Use computer-based training for flexible delivery, role-based exercises for job-specific decisions, and game-based scenarios for practice. Phishing simulations can help users recognize and report suspicious messages. Measure reporting, response, and learning over time, and use the results to improve training.

NIST · Cybersecurity Supply Chain Risk Management · NIST · Cybersecurity and Privacy Learning Program

Practice case

Retiring a vendor-connected legacy server. An unsupported billing server is still reachable through a vendor link. The team estimates an asset value of $100,000, a loss of 40% per incident, and one incident every two years. A replacement is ready, but the old server’s SSD holds records that may be subject to retention requirements.

What are the SLE and ALE under these assumptions? What would you record in the risk register? How would you manage the change and dispose of the SSD?

Review a possible answer

SLE is $100,000 × 0.40 = $40,000. ARO is 0.5 events per year, so ALE is $40,000 × 0.5 = $20,000 per year. Record the vendor access path, assumptions, business impact, risk owner, planned retirement date, and interim controls. Restrict vendor access while the old server is still needed and verify the restriction.

Approve and test the cutover, record a rollback plan, and verify billing and partner access on the replacement. Confirm that required records are preserved and any hold is resolved before sanitizing the SSD with a validated method suitable for flash media. Record disposition, remove obsolete access, and verify that the old service is unreachable.

Read and watch