Asset and Change Management

Overview

Asset Management: Ensures all devices (software and hardware) are identified, catalogued, and monitored.

Change Management: All modifications to systems are controlled and secure.

Acquisition and Procurement

Acquisition: Process of obtaining goods. Procurement: Encompasses full process of acquiring goods and services (includes previous steps).

The approval process for purchases ensures alignment with company’s goals and needs; unique to each organization.

Ways to Buy

  1. Company credit card: Useful for small, fast transactions (e.g., ink and toner).
  2. Individual purchase: Employees buy on company’s behalf and later seeks reimbursement from their employer.
  3. Purchase orders (PO): Formal document that authorizes a specific purchase for larger/more expensive items.

Mobile Device Deployments

Asset Management

Systematic approach to governing and maximizing value of items an entity is responsible for throughout their lifecycle.

Assignment/Accounting

Every asset is owned by an individual/group. There should be no ambiguity about who owns what. Classification: Categorizing assets based on function, value, or other relevant parameters.

Monitoring/Tracking

Ensures proper accountability and optimal use of each asset.

Asset Tracking: Involves maintain comprehensive inventory with asset specifications, locations, assigned users, and relevant details.

Enumeration: Involves identifying and counting assets during times of asset procurement or retirement. Used in especially large organizations.

Mobile Device Management (MDM): Lets organizations securely oversee employee devices, ensuring policy enforcement, software consistency and data protection. Centralization boosts security by ensuring all devices comply with latest standards and protocols. Lets IT remotely lock and wipe devices, mass-update/install applications, etc.

Asset Disposal

Special Publication 800-8, “Guidelines for Media Sanitization”

Sanitization

Process of making data inaccessible and irretrievable from a storage medium using traditional forensic methods.

  1. Overwriting: Replacing existing data with random bits of information to ensure original data is obscured.
  2. Degaussing: Degausser produces strong magnetic field that can disrupt magnetic domains on storage devices like HDDs or tapes. Device loses its data storage capability. Used when devices are being recycled/disposed.
  3. Secure Erase: Completely deletes data from a storage device while ensuring that it cannot be recovered using traditional recovery tools. Now replaced by Cryptographic Erase.
  4. Cryptographic Erase: Rather than erase the data, we just delete the encryption keys for a device. Very fast, especially for massive drives. Allows device to be trashed or resold.
  5. Destruction: Ensures physical device is beyond recovery or reuse (e.g., shredding, pulverizing, melting, incinerating).

Certification

Act of proof that data or hardware has been securely disposed of. Organizations should prioritize data security by documenting sanitization, disposal, or destruction of data.

Data Retention

Data retention is focused on strategically deciding what to keep and for how long. Regulations may require specific data to be retained for a set duration. The more you store, the more you must secure.

Change Management

Organizations orchestrated strategy to transition existing state for a more desirable future state.

Change Advisory Board (CAB): Body of representatives from various parts of an organization who are responsible for evaluating proposed changes.

Change Owner: Individual or team that initiates the change request.

Stakeholders

Stakeholder: Person who has a vested interest in the proposed change. You must inform/plan for your Technical Stakeholders, Business Stakeholders, and End-User Stakeholders.

Impact Management

  1. What could go wrong?
  2. What would be the immediate effects?
  3. How would long-term operations be impacted?
  4. Are there unforeseen challenges that might cause an issue?

Change Management Processes

Five steps:

  1. Preparation: Assessing the current state and recognizing the need for transition. Gather necessary resources, engage stakeholders, ensure preparedness.
  2. Vision for Change: Clear, compelling description of the desired future state that explains reasons and ensures vivid vision.
  3. Implementation: Put plan into action (Training, Restructuring teams, Introducing new technologies, Continuously communicate with stakeholder).
  4. Verification: Measure change’s effectiveness (Surveys, Performance metrics analysis, Stakeholders interviews).
  5. Documentation: Create thorough record of the entire change process.

Things to consider

  1. Use scheduled maintenance windows. Emergency changes can skip the window.
  2. Creation of a backout plan (Predetermined strategy for restoring systems to initial state in case a change does not go as planned).
  3. Testing of Results.
  4. Follows Standard Operating Procedure (SOP).

Technical Implications of Changes

Documenting Changes

What was done, when was it done, and why?

Version Control

Tracks and manage changes in documents and software, enabling collaborative work and rollbacks. Preserves history and ensures continuity and stability.

Proper Documentation

Properly document and record every change.

  1. Update diagrams.
  2. When encountering implementation issues, revise policies and procedures to prevent future occurrences.
  3. Update related change request or trouble ticket to indicate completion. This provides the audit log for the change.