NIST SP 800-46 Rev 2 Enterprise Telework, Remote Access and BYOD Security
Section 5: Security considerations for the telework and remote access life cycle – NIST SP 800-46 Rev 2 Enterprise Telework, Remote Access and BYOD Security

NIST SP 800-46 Rev 2 Enterprise Telework, Remote Access and BYOD Security 5.3: Test the implementation thoroughly and lock down defaults before production

What does 5.3 require?

Before production use the implementation is evaluated for connectivity, protection of communications (verified by monitoring traffic or checking logs rather than assumed), authentication, the range of applications that will be used over remote access, management, logging, performance, and the security of the implementation itself. Every component is brought up to the current patch level and configured to sound practice; implementers review each remote access setting's default, change those that fall short of the security requirements, and confirm the solution cannot revert to defaults for the sake of interoperability or anything else.

Maintained by Gerard Blokdyk

Other controls in Section 5: Security considerations for the telework and remote access life cycle – NIST SP 800-46 Rev 2 Enterprise Telework, Remote Access and BYOD Security

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll NIST SP 800-46 Rev 2 Enterprise Telework, Remote Access and BYOD Security controls