1. National Institute of Standards and Technology (NIST). (2020). Security and Privacy Controls for Information Systems and Organizations (Special Publication 800-53
Revision 5).
Control SC-7
Boundary Protection: The discussion section for this control states
"Boundary protection is a security design principle that involves isolating critical system components... This is achieved by controlling the flow of information between network segments." This directly supports using isolation for vulnerable
critical systems.
Control SI-2
Flaw Remediation: The discussion for this control acknowledges that for some components
flaw remediation may not be possible (as with EOL systems) and that organizations should "apply other mitigations." Network isolation is a primary example of such a mitigation.
2. University of California
Berkeley. (2023). Minimum Security Standard for Networked Devices. Information Security Office.
Section 5.1
Unsupported Software: This standard mandates that "Devices running unsupported software must be isolated from the network" or have other compensating controls approved. This illustrates that isolation is a standard
required practice for EOL systems in a formal security program.
3. Kim
D.
& Solomon
M. G. (2021). Fundamentals of Information Systems Security (4th ed.). Jones & Bartlett Learning.
In discussions on defense-in-depth and securing legacy systems
the text emphasizes network segmentation and isolation as key compensating controls when patching is not an option. It describes how firewalls and VLANs are used to create secure enclaves for critical assets that cannot be updated. (Chapter on Network Security).