Skip to content
Communications infrastructure
ASD ISMISM-1096

ASD ISM 1096 Ensure proper labelling of cables for identification

What it says

Cables are labelled at each end with sufficient source and destination details to enable the physical identification and inspection of the cable.

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

What it means

In plain English

Label cables on both ends for easy identification and inspection of where they start and end.

Labelling your cables at both ends helps you quickly identify which cable leads to what device. This is important because when something needs fixing or replacing, you don't want to waste time unplugging the wrong thing or creating a bigger mess.

Why it matters

Without clear labels at both ends, staff can disconnect the wrong cable, delaying fault isolation and causing avoidable outages during changes.

How to implement

  1. Office Manager: Ensure all network and power cables are labelled clearly at both ends with their source and destination.

    Use a label maker or durable tags and note the specific device or port each cable connects to.

  2. IT Team: Develop a standard labelling system for cables in your organisation.

    Create a guide to ensure consistency, using colours or codes that designate cable function and destination.

  3. Facilities Manager: Work with the IT team to implement the labelling system for new installations and during routine maintenance.

    Schedule regular checks to maintain the integrity of labels and replace any that are damaged or unreadable.

  4. Procurement: Source quality labelling materials that withstand environmental conditions such as humidity or temperature changes where applicable.

    Choose label materials that stick well and remain legible over time.

  5. Training Coordinator: Conduct brief training sessions for staff on the importance of cable labelling and how to label cables properly.

    This can be included in onboarding for new staff who work with or near these installations.

Keep it running

Label every cable at both ends with source and destination (rack, device, port), and update/replace labels after moves, adds and changes.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The cable labelling policy: Request a copy of the document or guide outlining the cable labelling procedures.

    Look at

    The specifics of the labelling system, including colour codes or naming conventions.

    Good evidence

    The policy is clear, up-to-date, and aligned with best practices.

  2. Check 2 of 5What an auditor asks for

    Ask for

    To see labelled equipment: Provide specific examples or a visual inspection of labelled cables at a sample workstation or server room.

    Look at

    Whether labels are consistent and readable on both ends of the cables.

    Good evidence

    Cables are clearly labelled and match the documented system.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Maintenance logs: Request logs or records showing routine checks of cable labels.

    Look at

    The frequency and detail of these checks.

    Good evidence

    Logs show regular checks with any issues promptly rectified.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Training records: Request proof of staff training on cable labelling.

    Look at

    Attendance records or training materials and dates.

    Good evidence

    Records show recent and relevant training sessions attended by the necessary personnel.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Procurement receipts or documentation: Request proof of purchased labelling materials.

    Look at

    Quality indicators such as material specifications.

    Good evidence

    Receipts show investments in durable, high-quality labelling materials that fit the organisation's standards.

Mappings

Closest match in ISO/IEC 27001: A.7.12, Secure cabling for power and data, which this control covers in full and more.

ISO 27001

ISO/IEC 27001: 1 mapping

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