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:
- TDA-17_A01 the developer of the system, system component or system service is required to demonstrate the use of a system development life cycle process that includes organization-defined system security engineering methods.
Assessment rigor: 1
Origin: 53A_R5_SA-04(03)(a) 53A_R5_SA-04(03)(b) 53A_R5_SA-04(03)(c) - TDA-17_A02 the developer of the system, system component or system service is required to perform attack surface reviews.
Assessment rigor: 1
Origin: 53A_R5_SA-11(06) - TDA-17_A03 the breadth of testing and evaluation of required controls is defined.
Assessment rigor: 1
Origin: 53A_R5_SA-11(07)_ODP[01] 53A_R5_SA-11_ODP[03] 53A_R5_SA-11_ODP[01] - TDA-17_A04 the depth of testing and evaluation of required controls is defined.
Assessment rigor: 1
Origin: 53A_R5_SA-11(07)_ODP[02] 53A_R5_SA-11_ODP[03] 53A_R5_SA-11_ODP[01] - TDA-17_A05 frequency at which to conduct testing/evaluation is defined.
Defined parameters: prior to each release to production, and at least annually
Assessment rigor: 1
Origin: 53A_R5_SA-11_ODP[02] 53A_R5_SA-11_ODP[01] - TDA-17_A06 the developer of the system, system component or system service is required at all post-design stages of the system development life cycle to develop a plan for ongoing security assessments.
Assessment rigor: 3
Origin: 53A_R5_SA-11a.[01] - TDA-17_A07 the developer of the system, system component or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing security assessments.
Assessment rigor: 3
Origin: 53A_R5_SA-11a.[02] - TDA-17_A08 the developer of the system, system component or system service is required at all post-design stages of the system development life cycle to develop a plan for privacy assessments.
Assessment rigor: 3
Origin: 53A_R5_SA-11a.[03] - TDA-17_A09 the developer of the system, system component or system service is required at all post-design stages of the system development life cycle to implement a plan for ongoing privacy assessments.
Assessment rigor: 3
Origin: 53A_R5_SA-11a.[04] - TDA-17_A10 the developer of the system, system component or system service is required at all post-design stages of the system development life cycle to perform testing/evaluation frequency to conduct at depth and coverage.
Defined parameters: prior to each release to production, and at least annually
Assessment rigor: 3
Origin: 53A_R5_SA-11b. - TDA-17_A11 the developer of the system, system component or system service is required at all post-design stages of the system development life cycle to produce evidence of the execution of the assessment plan.
Assessment rigor: 3
Origin: 53A_R5_SA-11c.[01] - TDA-17_A12 the developer of the system, system component or system service is required at all post-design stages of the system development life cycle to produce the results of the testing and evaluation.
Assessment rigor: 3
Origin: 53A_R5_SA-11c.[02] - TDA-17_A13 the developer of the system, system component or system service is required at all post-design stages of the system development life cycle to implement a verifiable flaw remediation process.
Assessment rigor: 3
Origin: 53A_R5_SA-11d. - TDA-17_A14 the developer of the system, system component or system service is required at all post-design stages of the system development life cycle to correct flaws identified during testing and evaluation.
Assessment rigor: 3
Origin: 53A_R5_SA-11e. - TDA-17_A15 the developer of the system, system component, or system service is required to verify that the scope of testing and evaluation provides complete coverage of the required controls per an organization-defined breadth.
Assessment rigor: 3
Origin: 53A_R5_SA-11(07)[01] - TDA-17_A16 the developer of the system, system component, or system service is required to verify that the scope of testing and evaluation provides complete coverage of the required controls per an organization-defined depth.
Assessment rigor: 3
Origin: 53A_R5_SA-11(07)[02]
Verknüpfte Vorgänge
| Verknüpfungstyp | Vorgang |
|---|---|
| blocks | Security, Compliance & Resilience Testing Throughout Development |
- 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.