1-minute read of a 4 min report

Huntress Maps Malware Checks Into NIST 800-171 Rev 3

By

1-minute read

What a defender needs to know

Three Revision 2 malware-protection requirements, 3.14.2, 3.14.4, and 3.14.5, map into Revision 3 requirement 03.14.02, according to Huntress’s November 20 transition guidance. Huntress says the old objective 3.14.2[a], which identifies designated locations, has no direct Revision 3 match. For defense contractors handling controlled unclassified information, the risk is a familiar endpoint policy that looks complete in the old crosswalk but misses the new wording about system entry and exit points, scan frequency, or response to detected malicious code.

Check which NIST SP 800-171 revision the active contract calls for. Keep Revision 2 evidence available for contracts using that revision, then map the existing endpoint policies and evidence to 03.14.02 for Revision 3 planning. Huntress identifies a frequency parameter in the new requirement; apply the value relevant to the customer or DoD contract and compare it with the actual scheduled scan setting. Its weekly scheduled-scan example describes Huntress’s baseline, not a default for every contractor.

For one endpoint and one entry or exit point in the CUI system boundary, inspect malware-protection coverage and assigned policies. Compare the scan schedule with the applicable parameter, and collect a recent event showing block, quarantine, or another configured response. Attach those artifacts, along with the update procedure, to the crosswalk. The blind spot is assuming a written policy establishes coverage on every system it names.

Primary sources