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-13_A01 acceptable mobile code technologies are defined.
Assessment rigor: 1
Origin: 53A_R5_SC-18a.[01] 53A_R5_SC-18a.[03] 171A_R3_A.03.13.13.a[02] - END-13_A02 unacceptable mobile code technologies are defined.
Assessment rigor: 1
Origin: 53A_R5_SC-18a.[02] 53A_R5_SC-18a.[04] 53A_R5_SC-18(01)[01] 53A_R5_SC-18(01)_ODP[01] - END-13_A03 the use of mobile code is authorized, monitored and controlled.
Assessment rigor: 1
Origin: 53A_R5_SC-18b.[01] 53A_R5_SC-18b.[02] 53A_R5_SC-18b.[03] 171A_3.13.13[a] 171A_3.13.13[b] - END-13_A04 the download of unacceptable mobile code is prevented.
Assessment rigor: 1
Origin: 53A_R5_SC-18(03)[01] - END-13_A05 the execution of unacceptable mobile code is prevented.
Assessment rigor: 1
Origin: 53A_R5_SC-18(03)[02] - END-13_A06 corrective actions to be taken when unacceptable mobile code is identified are defined.
Assessment rigor: 1
Origin: 53A_R5_SC-18(01)_ODP[02] - END-13_A07 corrective actions are taken if unacceptable mobile code is identified.
Assessment rigor: 1
Origin: 53A_R5_SC-18(01)[02] - END-13_A08 mobile code requirements for the acquisition, development and use of mobile code to be deployed in the system are defined.
Assessment rigor: 3
Origin: 53A_R5_SC-18(02)_ODP - END-13_A09 the acquisition of mobile code to be deployed in the system meets mobile code requirements.
Assessment rigor: 3
Origin: 53A_R5_SC-18(02)[01] - END-13_A10 the development of mobile code to be deployed in the system meets mobile code requirements.
Assessment rigor: 3
Origin: 53A_R5_SC-18(02)[02] - END-13_A11 the use of mobile code to be deployed in the system meets mobile code requirements.
Assessment rigor: 3
Origin: 53A_R5_SC-18(02)[03] - END-13_A12 unacceptable mobile code to be prevented from downloading and executing is defined.
Assessment rigor: 3
Origin: 53A_R5_SC-18(03)_ODP - END-13_A13 software applications in which the automatic execution of mobile code is to be prevented are defined.
Assessment rigor: 3
Origin: 53A_R5_SC-18(04)_ODP[01] - END-13_A14 actions to be enforced by the system prior to executing mobile code are defined.
Assessment rigor: 3
Origin: 53A_R5_SC-18(04)_ODP[02] - END-13_A15 the automatic execution of mobile code in software applications is prevented.
Assessment rigor: 3
Origin: 53A_R5_SC-18(04)[01] 53A_R5_SC-18(04)[02] - END-13_A16 platform-independent applications to be included within organizational systems are defined.
Assessment rigor: 3
Origin: 53A_R5_SC-27_ODP - END-13_A17 platform-independent applications are included within organizational systems.
Assessment rigor: 3
Origin: 53A_R5_SC-27 - END-13_A18 acceptable mobile code is defined.
Assessment rigor: 2
Origin: 171A_R3_A.03.13.13.a[01] - END-13_A19 the use of mobile code is authorized.
Assessment rigor: 2
Origin: 171A_R3_A.03.13.13.b[01] - END-13_A20 the use of mobile code is monitored.
Assessment rigor: 2
Origin: 171A_R3_A.03.13.13.b[02] - END-13_A21 the use of mobile code is controlled.
Assessment rigor: 2
Origin: 171A_R3_A.03.13.13.b[03]
Propojené úkoly
| Typ vazby | Úkol |
|---|---|
| blocks | Mobile Code |
- 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.