Skip to content
Networking
ASD ISMISM-2166

ASD ISM 2166 MACsec secure association lifetime limited to under four hours

What it says

A secure association lifetime of less than four hours (14400 seconds) is used for MACsec connections.

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

What it means

In plain English

Configure MACsec links so each secure association is replaced in under four hours (14400 seconds), limiting how long any one set of session keys stays in use on the link.

MACsec encrypts traffic between two directly connected network devices at the Ethernet layer. The encryption keys it uses are held in a "secure association" (SA), and the SA lifetime is how long one set of keys is used before the devices roll to a fresh one. This control requires that the SA lifetime on MACsec connections is set to less than four hours (14400 seconds). Keys that live for a long time give an attacker more time to collect traffic and more material encrypted under the same key. If a key is ever compromised, everything protected by it during its lifetime is exposed. Rekeying more often shrinks that window: the volume of data under any one key is smaller, and a compromised key becomes useless sooner. In short, a shorter SA lifetime limits how much traffic an attacker could ever decrypt from a single key.

Why it matters

If MACsec SA lifetimes are left at long or unlimited values, a single set of session keys protects hours or days of link traffic. A key compromise, a cryptographic weakness or a captured traffic stream then exposes far more data than it should, and the organisation cannot demonstrate that its encrypted links meet the ISM's rekeying expectation.

How to implement

  1. Network engineers should inventory every MACsec connection in the environment and record the currently configured secure association lifetime or rekey interval for each end of each link.

  2. Network engineers should set the MACsec SA lifetime (rekey timer) on every MACsec-capable device to a value below 14400 seconds, using the vendor's timer or key-lifetime parameter, and apply it consistently at both ends of each link.

  3. The network architecture owner should update the standard MACsec configuration template and build guide so the sub-four-hour lifetime is applied automatically to any new MACsec link.

  4. Network operations should add an automated configuration compliance check (for example a script or network configuration manager rule) that flags any MACsec interface whose SA lifetime is 14400 seconds or higher.

  5. The change manager should add a checklist item to MACsec-related changes, firmware upgrades and device replacements requiring the SA lifetime to be verified against the four-hour limit before the change is closed.

Keep it running

Treat the SA lifetime as a standard setting in the MACsec configuration template used for switches, routers and any other devices that terminate MACsec links. Network engineers should set the rekey interval (often expressed as a timer in seconds or minutes in vendor configuration) to a value below 14400 seconds and confirm that both ends of each link agree, since a mismatch can cause rekey failures or link flaps.

Day to day, watch for configuration drift: firmware upgrades, device replacements and copied configurations can silently reintroduce a vendor default that exceeds four hours. Include the SA lifetime in configuration compliance checks and in the change-approval checklist for any new or modified MACsec link. When troubleshooting MACsec links, do not "fix" instability by lengthening the lifetime beyond the limit; resolve the underlying key agreement issue instead.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    Ask for the list of all MACsec connections and the configured secure association lifetime for each end.

    Look at

    Check that every link is listed and that a lifetime value is recorded for both devices on each link.

    Good evidence

    Every MACsec link shows a lifetime below 14400 seconds at both ends, with no gaps or unknown values.

  2. Check 2 of 5What an auditor asks for

    Ask for

    Ask for running configuration exports from a sample of MACsec-enabled devices.

    Look at

    Find the MACsec or MKA policy section and read the rekey timer or key lifetime parameter.

    Good evidence

    The configured value is explicitly set below four hours rather than relying on an unstated vendor default.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Ask for the standard MACsec configuration template or build guide.

    Look at

    Look for the SA lifetime setting and the value it prescribes.

    Good evidence

    The template mandates a lifetime under 14400 seconds so new links inherit the setting automatically.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Ask for output from the configuration compliance tool or script that checks MACsec settings.

    Look at

    Check whether the SA lifetime is one of the checked parameters and review recent results.

    Good evidence

    Recent checks cover the lifetime, and any device found above the limit was remediated with a record of the fix.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Ask for change records for recent MACsec changes, firmware upgrades or device replacements.

    Look at

    Look for evidence that the SA lifetime was verified after the change.

    Good evidence

    Change records show the lifetime was confirmed below four hours before closure, demonstrating the setting survives routine changes.

Mappings

Closest match in ISO/IEC 27001: A.8.20, Network and network devices security, 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.