Protect against malicious code
- Last UpdatedNov 10, 2025
- 2 minute read
Malicious code protection begins with detection, proceeds to analysis, and then to protection measures. Protecting against malicious code requires a multi-faceted approach including access control, regular software patches, and segmentation and isolation of system components.
|
Step |
Action |
Notes Use this column to organize a deployment plan or to audit an existing plan. |
|
1 |
Implement malicious code protection mechanisms at system entry and exit points and at workstations, servers, or mobile computing devices. |
|
|
2 |
Update malicious code protection mechanisms whenever new releases are available in accordance with configuration management policy and procedures. |
|
|
3 |
Configure malicious code protection mechanisms to perform periodic scans of the system on a defined frequency and real-time scans of files from external sources as the files are downloaded, opened, or executed, and disinfect and quarantine infected files. |
Regular code reviews and static code analyses can add to automated tools and can reveal issues without running code. For ICS applications, this can be a means to test applications offline. |
|
4 |
Use malicious code protection software products from multiple vendors. |
|
|
5 |
Address any false positives received during malicious code detection and eradication and the resulting potential impact on the availability of the system. |
|
|
6 |
Centrally manage malicious code protection mechanisms. |
|
|
7 |
Implement automated updates to malicious code protection mechanisms and tools. |
Beyond malicious code tools, keep all software components up to date with the latest security patches. This helps protect against known vulnerabilities that could be exploited by malicious code. |
|
8 |
Implement access and authentication policies and rules to prevent users from circumventing host-based malicious code protection capabilities. |
Strict access controls can limit who can modify the code and access sensitive parts of the system. This reduces the risk of unauthorized changes. |
|
9 |
Minimize the number of privileged users who can update malicious code protection mechanisms. |
|
|
10 |
Tightly control - or completely prohibit - users from introducing removable media into the system. |
|
|
11 |
Include malicious code protection mechanisms to identify data containing malicious code and to respond accordingly when the system encounters data not explicitly allowed by the security policy. |
Intrusion Detection Systems (IDS) are one set of tools that can provide security. |
|
12 |
Ensure that centrally managing malicious code protection does not degrade the operational performance of the system. |