Assessment Objectives
In addition to relevant policies, standards and procedures, the assessor shall examine, interview, and/or test to determine if appropriately scoped evidence exists to support the claim that:
- END-04_A01 the frequency for malicious code scans is defined.
Defined parameters: at least weekly
Assessment rigor: 1
Origin: 171A_3.14.5[a] 53A_R5_SI-03_ODP[01] 53A_R5_SI-03_ODP[02] - END-04_A02 malicious code scans are performed with the defined frequency.
Defined parameters: at least weekly
Assessment rigor: 1
Origin: 171A_3.14.5[b] - END-04_A03 malicious code protection mechanisms are configured to perform real-time scans of files from external sources as the files are downloaded, opened or executed.
Assessment rigor: 1
Origin: 171A_3.14.5[c] - END-04_A04 designated locations for malicious code protection are identified.
Defined parameters: to include endpoints and network entry and exit points
Assessment rigor: 1
Origin: 171A_3.14.2[a] - END-04_A05 protection from malicious code at designated locations is provided.
Assessment rigor: 1
Origin: 171A_3.14.2[b] - END-04_A06 action to be taken in response to malicious code detection are defined.
Defined parameters: to include blocking and quarantining malicious code
Assessment rigor: 3
Origin: 53A_R5_SI-03_ODP[04] 53A_R5_SI-03_ODP[05] - END-04_A07 personnel or roles to be alerted when malicious code is detected is/are defined.
Defined parameters: administrator or defined security personnel, alerted in near real time
Assessment rigor: 3
Origin: 53A_R5_SI-03_ODP[06] - END-04_A08 malicious code protection mechanisms are implemented at system entry and exit points to detect malicious code.
Assessment rigor: 2
Origin: 53A_R5_SI-03_ODP[01] 53A_R5_SI-03a.[01] 171A_R3_A.03.14.02.a[01] - END-04_A09 malicious code protection mechanisms are implemented at system entry and exit points to eradicate malicious code.
Assessment rigor: 2
Origin: 53A_R5_SI-03_ODP[04] 53A_R5_SI-03a.[02] 171A_R3_A.03.14.02.a[02] - END-04_A10 malicious code protection mechanisms are updated automatically as new releases are available in accordance with organizational configuration management policy and procedures.
Assessment rigor: 3
Origin: 53A_R5_SI-03b. - END-04_A11 malicious code protection mechanisms are configured to perform periodic scans of the system frequency.
Defined parameters: at least weekly
Assessment rigor: 3
Origin: 53A_R5_SI-03c.01[01] - END-04_A12 malicious code protection mechanisms are configured to perform real-time scans of files from external sources as the files are downloaded, opened or executed in accordance with organizational policy.
Assessment rigor: 3
Origin: 53A_R5_SI-03c.01[02] - END-04_A13 malicious code protection mechanisms are configured to respond to malicious code detection.
Assessment rigor: 3
Origin: 53A_R5_SI-03c.02[01] 53A_R5_SI-03_ODP[04] - END-04_A14 malicious code protection mechanisms are configured to send alerts to personnel or roles in response to malicious code detection.
Assessment rigor: 3
Origin: 53A_R5_SI-03c.02[02] - END-04_A15 the receipt of false positives during malicious code detection and eradication and the resulting potential impact on the availability of the system are addressed.
Assessment rigor: 3
Origin: 53A_R5_SI-03d. - END-04_A16 malicious code protection mechanisms are implemented at system entry and exit points to eradicate malicious code.
Assessment rigor: 3
Origin: 53A_R5_SI-03a.[02] - END-04_A17 malicious code protection mechanisms are configured to block malicious code, quarantine malicious code, or take other actions in response to malicious code detection.
Assessment rigor: 2
Origin: 171A_R3_A.03.14.02.c.02 - END-04_A18 the frequency at which malicious code protection mechanisms perform scans is defined.
Defined parameters: at least weekly
Assessment rigor: 2
Origin: 171A_R3_A.03.14.02.ODP[01]
Verknüpfte Vorgänge
| Verknüpfungstyp | Vorgang |
|---|---|
| blocks | Malicious Code Protection (Antimalware) |
- Secure Controls Framework -
The Secure Controls Framework® (SCF)
"The SCF is the Common Controls Framework™ (CCF), the world's most comprehensive cybersecurity and data privacy metaframework - it is also free to use. The entire concept is building secure, compliant and resilient capabilities in the most efficient and cost-effective manner possible.
The SCF is more than just a unified control catalog, since its included content creates a playbook for Governance, Risk & Compliance (GRC) capabilities. Used globally by organizations of every size, the SCF is a robust and scalable solution for security, compliance and resilience controls. As a comprehensive security framework, the SCF maps 1,400+ controls across 200+ laws, regulations, and industry frameworks so you can implement once and comply everywhere.
Like it or not, cybersecurity is a protracted war on an asymmetric battlefield, where the threats are everywhere and as defenders we have to make the effort to work together to help improve cybersecurity and data privacy practices, since we all suffer when massive data breaches occur or when cyber attacks have physical impacts. Hackers share information on attack methods with other hackers, so why shouldn’t the good guys share information on how to best protect an organization? We decided to take action and make a difference, since we feel it is too important to wait for someone else to fix the problems that exist.
The SCF is made up of volunteers, mainly specialists within the cybersecurity profession, who focus on GRC and the cybersecurity side of data privacy. These are auditors, engineers, architects, incident responders, consultants and other specialists who live and breathe these topics on a daily basis. The end product is "expert-derived content" that makes up the SCF." https://securecontrolsframework.com/Terms & Conditions
The SCF End User License Agreement (EULA) governs the use of the Secure Controls Framework® (SCF) under the Creative Commons Attribution-No Derivatives 4.0 International Public License.