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:
- SEA-04_A01 an enterprise architecture is developed with consideration for cybersecurity / data privacy.
Assessment rigor: 1
Origin: 53A_R5_PM-07[01] 53A_R5_PM-07[03] - SEA-04_A02 an enterprise architecture is maintained with consideration for cybersecurity / data privacy.
Assessment rigor: 1
Origin: 53A_R5_PM-07[02] 53A_R5_PM-07[04] - SEA-04_A03 an enterprise architecture is developed with consideration for the resulting risk to organizational operations and assets, individuals and other organizations.
Assessment rigor: 1
Origin: 53A_R5_PM-07[05] - SEA-04_A04 an enterprise architecture is maintained with consideration for the resulting risk to organizational operations and assets, individuals and other organizations.
Assessment rigor: 1
Origin: 53A_R5_PM-07[06] - SEA-04_A05 frequency for review / update to reflect changes in the enterprise architecture.
Defined parameters: at least every 12 months, or when there are significant incidents or significant changes to risks
Assessment rigor: 3
Origin: 53A_R5_PL-08_ODP - SEA-04_A06 a cybersecurity / data privacy architecture for the system describes the requirements and approach to be taken for protecting the confidentiality, integrity and availability of organizational information.
Assessment rigor: 3
Origin: 53A_R5_PL-08a.01 53A_R5_PL-08a.02 - SEA-04_A07 a cybersecurity / data privacy architecture for the system describes how the architecture is integrated into and supports the enterprise architecture.
Assessment rigor: 3
Origin: 53A_R5_PL-08a.03[01] 53A_R5_PL-08a.03[02] - SEA-04_A08 a cybersecurity / data privacy architecture for the system describes any assumptions about and dependencies on external systems and services.
Assessment rigor: 3
Origin: 53A_R5_PL-08a.04[01] 53A_R5_PL-08a.04[02] - SEA-04_A09 changes in the enterprise architecture are reviewed / updated per an organization-defined frequency to reflect changes in the enterprise architecture.
Defined parameters: at least annually and when a significant change occurs
Assessment rigor: 3
Origin: 53A_R5_PL-08b. - SEA-04_A10 planned architecture changes are reflected in the cybersecurity / data privacy plan.
Assessment rigor: 3
Origin: 53A_R5_PL-08c.[01] 53A_R5_PL-08c.[02] - SEA-04_A11 planned architecture changes are reflected in the Concept of Operations (CONOPS).
Assessment rigor: 3
Origin: 53A_R5_PL-08c.[03] - SEA-04_A12 planned architecture changes are reflected in criticality analysis.
Assessment rigor: 3
Origin: 53A_R5_PL-08c.[04] - SEA-04_A13 planned architecture changes are reflected in organizational procedures.
Assessment rigor: 3
Origin: 53A_R5_PL-08c.[05] - SEA-04_A14 planned architecture changes are reflected in procurements and acquisitions.
Assessment rigor: 3
Origin: 53A_R5_PL-08c.[06]
Tickets liés
| Type de lien | Ticket |
|---|---|
| blocks | Alignment With Enterprise Architecture |
- 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.