Skip to content
Communications infrastructure
ASD ISMISM-0211

ASD ISM 0211 Develop and verify a cable register

What it says

A cable register is developed, implemented, maintained and regularly verified.

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

What it means

In plain English

Maintain a detailed record of cables and regularly check it for accuracy.

A cable register is like a detailed inventory list of all the cables used in your organisation. It's important because if cables are missing, outdated, or not working, it can cause communication problems, which leads to operational downtime and potential security risks.

Why it matters

Without a verified cable register, communications can fail unexpectedly, leading to costly downtime and potential security breaches.

How to implement

  1. Office managers should start by listing every type of cable used in the organisation, from network cables to power cords.

    They can walk through the office with a checklist to ensure nothing is missed, marking locations and types as they go.

  2. IT team should ensure the cable register includes information such as the cable type, location, function, and condition.

    This involves checking the physical state of each cable and noting any necessary repairs.

  3. Managers should schedule regular reviews of the cable register.

    This could be a monthly task assigned during team meetings, ensuring any changes in the infrastructure are updated immediately.

  4. Procurement should keep the register updated whenever new cables are purchased or old ones are discarded.

    They can coordinate with the IT team to understand what has been replaced and update records accordingly.

  5. Team leaders should train staff on the importance of reporting cable issues or changes so the register remains accurate.

    Regular quick reminders in team meetings can reinforce the importance of keeping the register current.

Keep it running

Regularly verify and update the cable register to prevent communication disruptions and maintain accurate infrastructure records.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    the latest version of the cable register document.

    Look at

    the update frequency and any recent changes.

    Good evidence

    an up-to-date document showing recent edits and a consistent updating schedule.

  2. Check 2 of 5What an auditor asks for

    Ask for

    to see documentation of recent cable maintenance or replacements.

    Look at

    if the maintenance aligns with items listed in the register as needing attention.

    Good evidence

    matching records for maintenance actions and register data.

  3. Check 3 of 5What an auditor asks for

    Look at

    how thorough the checks are on cable conditions and accuracy.

    Good evidence

    a well-documented process that verifies each entry in the register.

  4. Check 4 of 5What an auditor asks for

    Ask for

    training records that show staff are aware of procedures for updating the cable register.

    Look at

    the training frequency and staff completion rates.

    Good evidence

    current training logs with completion confirmations.

  5. Check 5 of 5What an auditor asks for

    Ask for

    to view past incidents related to cabling issues.

    Look at

    how these incidents were logged and resolved based on the register.

    Good evidence

    incidents tracked and clearly linked to register corrections.

Mappings

Closest match in ISO/IEC 27001: A.7.13, Proper maintenance of equipment, which partially overlaps with this control.

ISO 27001

ISO/IEC 27001: 1 mapping

  • A.7.13Proper maintenance of equipmentPartially overlaps

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