hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.2.1 FAU_GEN.1 Audit data generation | NOTE 1: The audit class of CC Part 2 [5] supports the requirements of Article 51 c/e/f from the CSA [i.13]. In ETSI TS 103 961 [1] requirements for audit in the event of errors are identified in clause 5, and the detail content of the records is defined in clause 7.3 of [1]. FAU_GEN.1.1 The TSF shall be able to generat... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.2.2 FAU_GEN.2 User identity association | NOTE: The audit class of CC Part 2 [5] supports the requirements of Article 51 c/e/f from the CSA [i.13]. FAU_GEN.2.1 For audit events resulting from actions of identified users, the TSF shall be able to associate each auditable event with the identity of the user that caused the event. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.2.3 FAU_SAR.1 Audit review | NOTE: The audit class of CC Part 2 [5] supports the requirements of Article 51 c/e/f from the CSA [i.13]. FAU_SAR.1.1 The TSF shall provide [assignment: authorised users] with the capability to read [assignment: list of audit information] from the audit records. FAU_SAR.1.2 The TSF shall provide the audit records in a ... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.2.4 FAU_SAR.2 Restricted audit review | NOTE: The audit class of CC Part 2 [5] supports the requirements of Article 51 c/e/f from the CSA [i.13]. FAU_SAR.2.1 The TSF shall prohibit all users read access to the audit records, except those users that have been granted explicit read-access. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.2.5 FAU_SAR.3 Selectable Audit Review | NOTE: The audit class of CC Part 2 [5] supports the requirements of Article 51 c/e/f from the CSA [i.13]. FAU_SAR.3.1 The TSF shall provide the ability to apply [assignment: methods of selection and/or ordering] of audit data based on [assignment: criteria with logical relations]. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.2.6 FAU_STG.2 Protected audit data storage | NOTE: The audit class of CC Part 2 [5] supports the requirements of Article 51 c/e/f from the CSA [i.13]. ETSI TS 103 961 [1] requires, in clause 7.3, that both configuration data and the audit trail of changes shall be maintained in a secure store. FAU_STG.2.1 The TSF shall protect the stored audit data in the audit t... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.2.7 FAU_STG.4 Action in case of possible audit data loss | NOTE: The audit class of CC Part 2 [5] supports the requirements of Article 51 c/e/f from the CSA [i.13]. FAU_STG.4.1 The TSF shall [store audit records in the database and export them into files] if the audit data storage exceeds [occupies over the default value of 80 % of the database capacity and lasts for over the ... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.3 User data protection | |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.3.1 FDP_ACC.1 Subset Access Control | Clause 7.2 of ETSI TS 103 961 [1] defines a number of requirements for access control which are met in part by FDP_ACC.1. • All data the NMS shall be made available to authorised entities using the principle of least privilege. • The access control mechanism shall follow the policy model outlined in ETSI TS 102 165-2 [... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.3.2 FDP_ACF.1 Security attribute-based access control | NOTE 1: The use of FDP_ACF.1 given below formalizes the access control rules defined in [1] with modifications as required to meet the formatting and wording of the CC SFRs. FDP_ACF.1.1 The TSF shall enforce the access control SFP to objects based on the following: • Subject: "User authentication status" with security ... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.4 Identity and authentication | |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.4.1 FIA_AFL.1 Authentication failure handling | FIA_AFL.1.1 The TSF shall detect when an administrator configurable positive integer within [assignment: range of acceptable values] unsuccessful authentication attempts occur related to [assignment: list of authentication events]. FIA_AFL.1.2 When the defined number of unsuccessful authentication attempts has been met... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.4.2 FIA_ATD.1 User attribute definition | A number of requirements from ETSI TS 103 963 [3] require the mapping of attributes to the NMS for the purpose of authentication, and for the assessment of access control privileges. FIA_ATD.1.1 The TSF shall maintain the following list of security attributes belonging to individual users: [assignment: list of security... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.4.3 FIA_UAU. 1 Timing of authentication | FIA_UAU.1.1 The TSF shall allow [assignment: list of TSF mediated actions] on behalf of the user to be performed before the user is authenticated. NOTE: In the context of the present document user refers only to an NMS administrator user, i.e. the user managing the protected assets (e.g. configuration data). FIA_UAU.1.... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.4.4 FIA_UAU.6 Re-authenticating | FIA_UAU.6.1 The TSF shall re-authenticate the user under the condition [assignment: list of conditions under which re-authentication is required]. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.4.5 FIA_UAU.7 Protected Authentication Feedback | FIA_UAU.7.1 The TSF shall provide only [assignment: list of feedback] to the user while the authentication is in progress. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.4.6 FIA_UID.1 Timing of identification | In accordance with the least privilege principle, the TSF shall not allow any operational actions by unidentified entities. In addition, as the TSF is mostly deployed without a direct user (i.e. it operates autonomously) the mediated actions shall always be restricted. In this regard therefore, the only actions enabled... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.5 Cryptographic Support | |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.5.1 FCS_CKM.1 Cryptographic key generation | NOTE 1: As the base requirements from ETSI TS 103 963 [3] do not specify cryptography, the specific wording of assignments in the SFRs from [5] are omitted in the present document, but are expected to be provided in detail in any corresponding ST. The relevant parts are highlighted in clauses 9.5.2 through 9.5.5. NOTE ... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.5.2 FCS_CKM.2 Cryptographic key distribution | FCS_CKM.2.1 The TSF shall distribute cryptographic keys in accordance with a specified cryptographic key distribution method [assignment: cryptographic key distribution method] that meets the following: [assignment: list of standards]. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.5.3 FCS_CKM.3 Cryptographic key access | FCS_CKM.3.1 The TSF shall perform [assignment: type of cryptographic key access] in accordance with a specified cryptographic key access method [assignment: cryptographic key access method] that meets the following: [assignment: list of standards]. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.5.4 FCS_CKM.6 Timing and event of cryptographic key destruction | FCS_CKM.6.1 The TSF shall destroy [assignment: list of cryptographic keys (including keying material)] when [selection: no longer needed, [assignment: other circumstances for key or keying material destruction]]. FCS_CKM.6.2 The TSF shall destroy cryptographic keys and keying material specified by FCS_CKM.6.1 in accord... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.5.5 FCS_COP.1.1 Cryptographic operation | FCS_COP.1.1 The TSF shall perform [assignment: list of cryptographic operations] in accordance with a specified cryptographic algorithm [assignment: cryptographic algorithm] and cryptographic key sizes [assignment: cryptographic key sizes] that meet the following: [assignment: list of standards]. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.6 Security management class | |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.6.1 FMT_SMF.1 Specification of Management Functions | FMT_SMF.1.1 The TSF shall be capable of performing the following management functions: [assignment: • Assignment of privileges and rights to user roles • Management of user accounts • list of management functions to be provided by the TSF ]. ETSI ETSI TS 104 013 V1.1.1 (2026-01) 31 |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.6.2 FMT_MOF.1 Management of Security Functions Behaviour | FMT_MOF.1.1 The TSF shall restrict the ability to [selection: determine the behaviour of, disable, enable, modify the behaviour of] the functions [assignment: list of functions] to [assignment: the authorised identified roles]. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.6.3 FMT_MSA.1 Management of security attributes | The TSF shall enforce the [assignment: access control SFP(s), information flow control SFP(s)] to restrict the ability to [selection: change_default, query, modify, delete, [assignment: other operations]] the security attributes [assignment: list of security attributes] to [assignment: the authorised identified roles]. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.6.4 FMT_SMR.1 Security roles | FMT_SMR.1.1 The TSF shall maintain the roles [assignment: the authorised identified roles]. FMT_SMR.1.2 The TSF shall be able to associate users with roles. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.6.5 FMT_MSA.3 Static attribute initialization | FMT_MSA.3.1 The TSF shall enforce the [assignment: access control SFP, information flow control SFP] to provide [selection, choose one of: restrictive, permissive, [assignment: other property]] default values for security attributes that are used to enforce the SFP. FMT_MSA.3.2 The TSF shall allow the [assignment: the ... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.6.6 FMT_MTD.1 Management of TSF Data | FMT_MTD.1.1 The TSF shall restrict the ability to [selection: change_default, query, modify, delete, clear, [assignment: other operations]] the [assignment: list of TSF data] to [assignment: the authorised identified roles]. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.7 TOE Access | |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.7.1 FTA_TSE.1 TOE Session Establishment | FTA_TSE.1.1 The TSF shall be able to deny session establishment based on [assignment: attributes]. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.7.2 FTA_SSL.3 TSF-initiated Termination | FTA_SSL.3.1 The TSF shall terminate an interactive session after a [assignment: time interval of user inactivity]. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.7.3 FTA_SSL.4 User-initiated Termination | FTA_SSL.4.1 The TSF shall allow user-initiated termination of the user's own interactive session. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.7.4 FTA_TAH.1 TOE Access History | FTA_TAH.1.1 Upon successful session establishment, the TSF shall display the [selection: date, time, method, location] of the last successful session establishment to the user. FTA_TAH.1.2 Upon successful session establishment, the TSF shall display the [selection: date, time, method, location] of the last unsuccessful... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.8 Trusted Path class | |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.8.1 FTP_TRP.1 Trusted Path | FTP_TRP.1.1 The TSF shall provide a communication path between itself and [selection: remote, local] users that is logically distinct from other communication paths and provides assured identification of its end points and protection of the communicated data from [selection: modification, disclosure, [assignment: other... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 9.8.2 FTP_ITC.1 Inter-TSF trusted channel | FTP_ITC.1.1 The TSF shall provide a communication channel between itself and another trusted IT product that is logically distinct from other communication channels and provides assured identification of its end points and protection of the channel data from modification or disclosure. FTP_ITC.1.2 The TSF shall permit ... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 10 SAR Components | |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 10.1 Additional SAR components | |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 10.1.1 SAR SW Patch Management | SAR SW Patch Management is formed to include these aspects into the TOE evaluation in order to verify the correctness of the assigned SFRs and SARs. SAR Vulnerability processing has been added to the TOE. Passing the evaluation provides the basis for the conformance statement for the assigned SFRs and SARs. |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 10.1.2 SAR augmentation: ALC_FLR.2 Flaw reporting procedures | NOTE: The CC uses the term "security flaw" where other documentation (e.g. from ETSI) and EU regulation uses the term "security vulnerability". The terms appear to be identical in intent and the broad recommendation in [1] and [2] to adopt the guidance of ETSI TR 103 838 [i.2] and to implement the security controls of ... |
a6e30bb789283d6250af7e65d14a1c87 | 104 013 | 10.2 Dependencies of Assurance Components | The writer of any ST conforming to the present document shall consider the inter-dependencies of the SARs as defined in [6] and claimed in clause 4 of the present document with the targeted evaluation assurance level. ETSI ETSI TS 104 013 V1.1.1 (2026-01) 37 Annex A (informative): Mapping between base requirements and ... |
c94756e4aa7c166fd2e3d23d16d8bedc | 104 151-2 | 1 Scope | The present document provides the Implementation Conformance Statement (ICS) pro forma for testing Server implementations for compliance to the Mission Critical Services over LTE protocol requirements defined by 3GPP, and in accordance with the relevant guidance given in ISO/IEC 9646-1 [i.6] and ISO/IEC 9646-7 [2]. The... |
c94756e4aa7c166fd2e3d23d16d8bedc | 104 151-2 | 2 References | |
c94756e4aa7c166fd2e3d23d16d8bedc | 104 151-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
c94756e4aa7c166fd2e3d23d16d8bedc | 104 151-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
c94756e4aa7c166fd2e3d23d16d8bedc | 104 151-2 | 3 Definitions, symbols and abbreviations | |
c94756e4aa7c166fd2e3d23d16d8bedc | 104 151-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply: NOTE 1: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). In addition for the purpos... |
c94756e4aa7c166fd2e3d23d16d8bedc | 104 151-2 | 3.2 Symbols | Void. |
c94756e4aa7c166fd2e3d23d16d8bedc | 104 151-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply: NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). ICS Implementation ... |
c94756e4aa7c166fd2e3d23d16d8bedc | 104 151-2 | 4 Recommended Test Case Applicability | The applicability of each individual test is identified in Table 4-1 (MCVideo Server). This is just a recommendation based on the purpose for which the test case was written. The applicability of every test is formally expressed by the use of Boolean expression that are based on parameters (ICS) included in annex A of ... |
18c8d791e85b7f57392db2bcf1248e26 | 104 153-1 | 1 Scope | The present document provides the Protocol Implementation Conformance Statement (PICS) pro forma for the test specification for the IP/ICMP Translation Algorithm as specified in IETF RFC 7915 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [2] and ET... |
18c8d791e85b7f57392db2bcf1248e26 | 104 153-1 | 2 References | |
18c8d791e85b7f57392db2bcf1248e26 | 104 153-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
18c8d791e85b7f57392db2bcf1248e26 | 104 153-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
18c8d791e85b7f57392db2bcf1248e26 | 104 153-1 | 3 Definition of terms, symbols and abbreviations | |
18c8d791e85b7f57392db2bcf1248e26 | 104 153-1 | 3.1 Terms | For the purposes of the present document, the terms given in IETF RFC 7915 [1] and the following apply: PICS pro forma: document, in the form of a questionnaire, designed by the protocol specifier or conformance test suite specifier, which, when completed for an OSI implementation or system, becomes the PICS NOTE: See ... |
18c8d791e85b7f57392db2bcf1248e26 | 104 153-1 | 3.2 Symbols | Void. |
18c8d791e85b7f57392db2bcf1248e26 | 104 153-1 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in IETF RFC 7915 [1] and the following apply: 3GPP 3rd Generation Partnership Project AH Authentication Header ATS Abstract Test Suite DCCP Datagram Congestion Control Protocol DF Don't Fragment ESP Encapsulating Security Payload ICMP Internet Control Me... |
18c8d791e85b7f57392db2bcf1248e26 | 104 153-1 | 4 Conformance | A PICS pro forma which conforms to this PICS pro forma specification shall be technically equivalent to annex A, and shall preserve the numbering and ordering of the items in annex A. A PICS which conforms to this PICS pro forma specification shall: a) describe an implementation which claims to conform to IETF RFC 7915... |
cc9787fab9d1cbf1a057f655ddd1d77a | 104 152-2 | 1 Scope | The present document provides the Implementation Conformance Statement (ICS) pro forma for testing Server implementations for compliance to the Mission Critical Services over LTE protocol requirements defined by 3GPP, and in accordance with the relevant guidance given in ISO/IEC 9646-1 [i.6] and ISO/IEC 9646-7 [2]. The... |
cc9787fab9d1cbf1a057f655ddd1d77a | 104 152-2 | 2 References | |
cc9787fab9d1cbf1a057f655ddd1d77a | 104 152-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
cc9787fab9d1cbf1a057f655ddd1d77a | 104 152-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
cc9787fab9d1cbf1a057f655ddd1d77a | 104 152-2 | 3 Definitions, symbols and abbreviations | |
cc9787fab9d1cbf1a057f655ddd1d77a | 104 152-2 | 3.1 Definitions | For the purposes of the present document, the terms given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply: NOTE 1: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). In addition for the purposes of the presen... |
cc9787fab9d1cbf1a057f655ddd1d77a | 104 152-2 | 3.2 Symbols | Void. |
cc9787fab9d1cbf1a057f655ddd1d77a | 104 152-2 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 121 905 [i.1] (3GPP TR 21.905) and the following apply: NOTE: An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in ETSI TR 121 905 [i.1] (3GPP TR 21.905). ICS Implementation ... |
cc9787fab9d1cbf1a057f655ddd1d77a | 104 152-2 | 4 Recommended Test Case Applicability | The applicability of each individual test is identified in Table 4-1 (MCVideo Server). This is just a recommendation based on the purpose for which the test case was written. The applicability of every test is formally expressed by the use of Boolean expression that are based on parameters (ICS) included in annex A of ... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 1 Scope | The present document specifies the key aspects of Continuous Auditing-Based Conformity Assessment (CABCA) as an audit methodology to evaluate and assess an AI system's conformity to relevant standards and regulations in a continuous manner. The present document applies to all types of organizations involved in the qual... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 2 References | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 3 Definition of terms, symbols and abbreviations | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 3.1 Terms | For the purposes of the present document, the following terms apply: AI - risk management frameworks: guidelines and best practices for identifying, assessing, and mitigating risks associated with Artificial Intelligence (AI) systems, such as machine learning models, to ensure their safe and responsible use AI system: ... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 3.2 Symbols | Void. |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AI Artificial Intelligence API Application Programming Interface CABCA Continuous Auditing-Based Conformity Assessment CE Conformité Européenne ER Entity-Relationship ESO European Standardization Organization GDPR General Data Protection Regul... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 4 CABCA Motivation and Overview | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 4.1 Imperative of CABCA in AI System Assurance | The European Union's Artificial Intelligence Act (EU AI Act) [i.9] establishes comprehensive obligations for providers of high-risk AI systems, encompassing critical areas such as risk management (Art. 9), technical documentation (Art. 11), quality management (Art. 17), conformity assessment (Art. 43), the EU Declarati... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 4.2 Comparison of CABCA with Traditional Audit Processes | Figure 4.2‑1: CABCA comparison to a traditional audit While CABCA serves the fundamental audit objective of evaluating conformity against requirements, its operational structure differs significantly from a traditional generic audit process, such as one guided by ISO 19011:2018 [2]. The simplified process flows illustr... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5 Fundamentals of CABCA | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.1 General | CABCA is a dynamic methodology designed for the continuous assessment of an AI system's adherence to relevant requirements. CABCA implementation is established on a per-system basis, as this allows for the necessary specificity in auditing. However, the framework and the operationalization logic developed for one syste... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.2 Mandatory Prerequisites for Implementing CABCA | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.2.1 General | Successful implementation and operation of the CABCA methodology shall be contingent upon the organization meeting specific mandatory prerequisites. These prerequisites represent the necessary input conditions and foundational capabilities required before CABCA can be effectively applied. They are distinct from the cap... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.2.2 Comprehensive Knowledge Base | Organizations shall possess and maintain a comprehensive knowledge base relevant to the AI systems under assessment, which shall include: a) Understanding of conformity requirements: Organizations shall possess and maintain a deep and current understanding of the specific conformity requirements applicable to the AI sy... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.2.3 Technical and Operational Expertise | Organizations shall ensure they possess the necessary technical and operational expertise, including: a) Operationalization skills: Demonstrated ability to translate high-level conformity specifications and requirements (from standards, regulations, and ethical guidelines) into specific, actionable, measurable, and mac... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.2.4 Infrastructure and Methodological Framework | Organizations shall have in place an adequate infrastructure and methodological framework, which shall include: a) Continuous monitoring infrastructure: A robust and reliable technological infrastructure capable of supporting continuous monitoring, data collection, evidence processing, and automated analysis as require... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.2.5 Risk Management and Stakeholder Engagement | Organizations shall demonstrate effective risk management and stakeholder engagement capabilities, including: a) Risk management proficiency: Proficiency in identifying, assessing, and mitigating risks associated with AI systems, specifically tailored to the context of continuous auditing and conformity assessment as p... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.3 Basic Assumptions of CABCA | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.3.1 General | This clause describes the fundamental assumptions that underpin the CABCA framework that are also essential for quality management systems, including post-market monitoring and being in compliance with ISO 9001:2015 [3] - Quality management systems. These assumptions relate to the nature and characteristics of AI syste... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.3.2 AI System Heterogeneity and Dynamism | CABCA assumes that while AI systems vary widely in complexity, function, and application domain, they are subject to common, universal requirements. These requirements are often derived from high-level ethical principles, such as fairness, transparency, technical robustness, and accountability, which are foundational t... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.3.3 Universal Applicability and Transparency | Building on the existence of common requirements, CABCA further assumes that the specific standards, regulations, and ethical guidelines selected for assessment can be consistently interpreted and practically operationalized (i.e. translated into measurable metrics and verifiable tests) for any type of AI system, ensur... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.3.4 Independence and Objectivity in Auditing | The integrity and credibility of CABCA rely on maintaining independence and objectivity throughout the auditing process, whether internal or external. This is not only an assumption, but a fundamental requirement supported by several facets of the CABCA framework. Independence is fostered through several mechanisms. Th... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.4 Principles of CABCA | |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.4.1 General | CABCA is founded on three guiding principles: ongoing conformity, stakeholder trust, and adaptability [i.7], [i.8]. The rationale for their selection is as follows: • Ongoing conformity was chosen to directly counter the limitations of traditional 'point-in-time' audits, which are inadequate for the dynamic nature of A... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.4.2 Ongoing conformity | Traditional conformity assessment methodologies often offer a 'snapshot' of compliance at a particular moment in time. While this approach may suffice for static or slowly evolving systems, it is inadequate for rapidly changing environments, particularly in sectors like Machine Learning. CABCA shifts this paradigm by f... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.4.3 Stakeholder trust | Trust is a crucial element for any organization's success, especially in today's rapidly changing landscape. The CABCA methodology places a high value on transparency and open communication with stakeholders, which in turn fosters trust. As detailed in clause 5.1, CABCA achieves this by establishing foundational trust ... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 5.4.4 Adaptability | CABCA is designed for adaptability, enabling it to keep pace with changes in AI systems, emerging risks, and the external regulatory landscape. This principle is crucial for dynamically evolving systems like Machine Learning, where static auditing methods fall short. It is put into practice through the Operationalizati... |
700e2f9cc025d565da15725694fe1bf2 | 104 008 | 6 Description of the CABCA Process Execution |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.