SC-40 asks you to protect internal and external wireless links from signal parameter attacks that you specify. These are attacks on the radio signal itself, as opposed to the data inside it.
800-53 binds federal systems and their contractors. If you run Wi-Fi, cellular or other radio links and a customer asks about them, this control is the reference.
What it means in practice
NIST explains that adversaries can exploit the signal parameters of wireless links to gain intelligence, deny service or spoof users. It also says that if you rely on commercial providers for commodity transmission service, you may not be able to implement these protections fully. Say so openly in your documentation. An honest scope note beats a claim you cannot back.
The enhancements show the range: SC-40(1) Electromagnetic Interference, SC-40(2) Reduce Detection Potential, SC-40(3) Imitative or Manipulative Communications Deception, and SC-40(4) Signal Parameter Identification. Most are for military style links. A commercial office usually stops at the basics.
Evidence to collect
- An inventory of wireless links, internal and external.
- Wireless controller configuration: WPA3 or WPA2 Enterprise, management frame protection, rogue access point detection.
- Provider documents for links you do not own, with the limits written down.
Common gaps
Guest and corporate networks sharing infrastructure. No rogue access point alerts. Wireless links on industrial or retail equipment missing from the inventory.
How to implement it
List every link, enable management frame protection and rogue detection, and record what you cannot control. Review the list yearly.
Quick check
What can you do if a commercial provider runs the link?
Document that the provider limits what you can implement, and show the compensating steps you took.
