Skip to content
Communications infrastructure
ASD ISMISM-0206

ASD ISM 0206 Develop and maintain cable labelling processes

What it says

Cable labelling processes, and supporting cable labelling procedures, are developed, implemented and maintained.

Quoted as published. Everything else on this page is written by Control Stack.

What it means

In plain English

Ensure cables are labelled correctly by setting up and following specific procedures.

This control is about making sure the cables in your organisation are correctly labelled. This is important because poorly labelled cables can lead to confusion, delays in fixing issues, and can even cause people to unplug the wrong connections, resulting in downtime or data loss.

Why it matters

Mislabelled cables can cause critical outages, leading to service disruptions and increased recovery time in fault scenarios.

How to implement

  1. Assign a responsible person: The office manager or IT coordinator should oversee the cable labelling process.

    They should document and regularly update the procedures to ensure that all cables are consistently labelled across the organisation.

  2. Create a consistent labelling method: The IT team should develop a system that includes using durable labels with clear text for identifying cables.

    This could involve pre-printed labels or a colour-coding system to differentiate between types of cables.

  3. Conduct training sessions: The office manager should organise regular training sessions for staff to familiarise them with the labelling system and procedures.

    Provide guides or cheat sheets for quick reference.

  4. Schedule regular checks: The IT team should conduct regular inspections to ensure cable labels are still clear and haven't been removed or damaged.

    Schedule these checks to coincide with routine maintenance visits.

  5. Document procedure changes: Whenever cable labelling procedures are updated, ensure the changes are documented and communicated to all relevant staff.

    This should include what was changed, why it was changed, and how it should be implemented moving forward.

Keep it running

Regularly audit cable labels and ensure adherence to standards; mislabelling often surfaces during maintenance or troubleshooting.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The cable labelling procedure document: Check that this document exists and details all steps and responsibilities.

    Good evidence

    Includes version control, the author's name, and the date of the last update.

  2. Check 2 of 5What an auditor asks for

    Look at

    The labels on cables in a sample area: Verify they match the documented procedures.

    Good evidence

    Would be legible labels that follow the described system, such as colour code or text description.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Them to explain how they apply and maintain labels.

    Good evidence

    Will include an understanding of the procedure, tools used, and a description of the last time it was updated or reviewed.

  4. Check 4 of 5What an auditor asks for

    Good evidence

    Is that the responsible person follows steps as per the documentation without confusion.

  5. Check 5 of 5What an auditor asks for

    Look at

    Tickets or emails about mislabelled cables and how they were resolved.

    Good evidence

    Includes details of corrective actions taken and any procedure amendments that resulted from the incident.

Mappings

Closest match in ISO/IEC 27001: A.5.37, Documented operating procedures for information processing, which this control partially meets.

ISO 27001

ISO/IEC 27001: 2 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.