3.14.2—System and Information Integrity - Basic
>Control Description
>Discussion
Designated locations include system entry and exit points which may include firewalls, remote-access servers, workstations, electronic mail servers, web servers, proxy servers, notebook computers, and mobile devices. Malicious code includes viruses, worms, Trojan horses, and spyware. Malicious code can be encoded in various formats (e.g., UUENCODE, Unicode), contained within compressed or hidden files, or hidden in files using techniques such as steganography.
Malicious code can be inserted into systems in a variety of ways including web accesses, electronic mail, electronic mail attachments, and portable storage devices. Malicious code insertions occur through the exploitation of system vulnerabilities. Malicious code protection mechanisms include anti-virus signature definitions and reputation-based technologies.
A variety of technologies and methods exist to limit or eliminate the effects of malicious code. Pervasive configuration management and comprehensive software integrity controls may be effective in preventing execution of unauthorized code. In addition to commercial off-the-shelf software, malicious code may also be present in custom-built software.
This could include logic bombs, back doors, and other types of cyber-attacks that could affect organizational missions/business functions. Traditional malicious code protection mechanisms cannot always detect such code. In these situations, organizations rely instead on other safeguards including secure coding practices, configuration management and control, trusted procurement processes, and monitoring practices to help ensure that software does not perform functions other than the functions intended. [SP 800-83] provides guidance on malware incident prevention.
>Cross-Framework Mappings
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What policies govern identification and authentication for devices?
- •What procedures define device identity verification?
- •Who approves device authentication requirements?
- •How do you handle device enrollment and identity management?
- •What governance ensures all devices are authenticated before access?
Technical Implementation:
- •What methods authenticate devices before network access?
- •How do you implement 802.1X or device certificates?
- •What network access control (NAC) solutions authenticate devices?
- •How do you enforce device authentication policies?
- •What monitoring tracks device authentication events?
Evidence & Documentation:
- •Can you provide device authentication policies and configurations?
- •What evidence shows devices are authenticated before access?
- •Can you demonstrate NAC or 802.1X implementation?
- •What logs track device authentication activities?
- •What audit findings verify device authentication compliance?
Ask AI
Configure your API key to use AI features.