Skip to content
Communications infrastructure
ASD ISMISM-1112

ASD ISM 1112 Ensure cables are inspectable every five metres

What it says

Cables in non-TOP SECRET areas are inspectable every five metres or less.

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

What it means

In plain English

Cables outside TOP SECRET areas should be easy to inspect every five metres for security checks.

This control ensures that cables used outside of highly secure areas, like TOP SECRET zones, can be easily inspected every five metres. It's important because any damage or tampering with cables could allow unauthorised access to sensitive information, leading to data breaches or security incidents.

Why it matters

Failure to inspect cables every five metres may enable undetected tampering, exposing the organisation to potential data breaches.

How to implement

  1. Building managers should ensure that cable installations are planned with inspectability in mind.

    This involves consulting with engineers to map out routes where cables can be easily inspected every five metres, placing them in areas that allow easy visual checks.

  2. IT and maintenance teams should set up regular inspection schedules.

    This means assigning team members to visually inspect each five-metre segment of cabling at routine intervals, looking for signs of wear or tampering.

  3. Procurement teams should purchase cabling solutions that support this requirement.

    They should look for products designed with access panels or points every five metres, which can make the inspection process much simpler.

  4. Trainers or safety officers should conduct briefing sessions for staff involved in cabling maintenance.

    They should explain why five-metre inspections are crucial, demonstrating how to properly check cables and what issues to look out for.

  5. System owners should document all cabling routes and inspection points.

    They need to create detailed plans and logs that are easily accessible, so any person involved in security audits can quickly verify the setup.

Keep it running

Design cable routes so all runs are visually inspectable at least every five metres (or less); add access panels/points and avoid concealed segments between inspection intervals.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The cable layout plans: Request maps or documentation showing where all cables are laid out.

    Look at

    The details to ensure inspection points are marked every five metres.

    Good evidence

    Includes clear plans with all required inspection points highlighted.

  2. Check 2 of 5What an auditor asks for

    Look at

    The consistency of inspections carried out, noting any documentation of repairs or faults found.

    Good evidence

    Is a completed log showing regular checks, with any issues properly documented and addressed.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Maintenance team training records: Request proof of training sessions that cover cable inspection procedures.

    Look at

    The dates and attendance records for these sessions.

    Good evidence

    Includes recent training records with most team members attending.

  4. Check 4 of 5What an auditor asks for

    Ask for

    The purchase specifications for cabling.

    Look at

    The criteria that demonstrate support for regular inspections, such as product details or supplier assurances.

    Good evidence

    Is documentation showing products that accommodate regular inspection requirements.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Incident response records related to cabling: Request any recorded incidents of cable distortion or tampering.

    Look at

    Details on how these issues were detected and resolved.

    Good evidence

    Includes incident records showing prompt and effective responses to cable-related issues.

Mappings

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

ISO 27001

ISO/IEC 27001: 1 mapping

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