+Airteagal 30 Rialacha agus coinníollacha maidir leis an marcáil CE a ghreamú
---+Airteagal 30 1.
---+Airteagal 30 2.
---+Airteagal 30 3.
---+Airteagal 30 4.
---+Airteagal 30 5.
---+Airteagal 30 6.

Airteagal 30 Rialacha agus coinníollacha maidir leis an marcáil CE a ghreamú

-

1. Forbhreathnú

,
Airteagal 30 1.
Déanfar an mharcáil CE a ghreamú go feiceálach, go soléite agus go doscriosta den táirge ag a bhfuil eilimintí digiteacha. I gcás nach féidir é sin a dhéanamh nó nach bhfuil údar leis mar gheall ar chineál an táirge ag a bhfuil eilimintí digiteacha, greamófar í den phacáistíocht agus de dhearbhú comhréireachta AE dá dtagraítear in Airteagal 28 a ghabhann leis an táirge ag a bhfuil eilimintí digiteacha. I gcás táirgí ag a bhfuil eilimintí digiteacha atá i bhfoirm bogearraí, greamófar an mharcáil CE de dhearbhú comhréireachta AE dá dtagraítear in Airteagal 28 nó beidh sí ar an suíomh gréasáin a ghabhann leis an táirge bogearraí. Sa chás deireanach sin, beidh rochtain éasca agus dhíreach ag tomhaltóirí ar an roinn ábhartha den suíomh gréasáin.
Airteagal 30 2.
Mar gheall ar chineál an táirge ag a bhfuil eilimintí digiteacha, féadfaidh airde na marcála CE a ghreamaítear den táirge ag a bhfuil eilimintí digiteacha a bheith níos ísle ná 5 mm, ar choinníoll go mbeidh sí fós infheicthe agus inléite.
Airteagal 30 3.
Greamófar an mharcáil CE den táirge ag a bhfuil eilimintí digiteacha sula gcuirfear ar an margadh é. Féadfar picteagram nó aon mharc eile lena léirítear riosca cibearshlándála nó úsáid ar leith a leagtar amach sna gníomhartha cur chun feidhme dá dtagraítear i mír 6 a chur i ndiaidh na marcála CE.
Airteagal 30 4.
I ndiaidh na marcála CE, beidh uimhir aitheantais an chomhlachta faoina dtugtar fógra, i gcás ina bhfuil baint ag an gcomhlacht sin leis an nós imeachta um measúnú comhréireachta atá bunaithe ar dhearbhú cáilíochta iomlán (bunaithe ar mhodúl H) dá dtagraítear in Airteagal 32.

Is é an comhlacht féin a ghreamóidh uimhir aitheantais an chomhlachta faoina dtugtar fógra, sin nó an monaróir nó ionadaí údaraithe an mhonaróra, ach treoir chuige sin a fháil ón gcomhlacht sin.
Airteagal 30 5.
Cuirfidh na Ballstáit leis na sásraí atá ann cheana chun a áirithiú go gcuirfear i bhfeidhm i gceart an córas lena rialaítear an mharcáil CE agus déanfaidh siad beart iomchuí i gcás ina mbaintear úsáid mhíchuí as an marcáil sin. I gcás ina bhfuil an táirge ag a bhfuil eilimintí digiteacha faoi réir reachtaíocht an Aontais um chomhchuibhiú, seachas an Rialachán seo, lena ndéantar foráil freisin maidir leis an marcáil CE a ghreamú, tabharfar le fios ar an marcáil CE go gcomhlíonann an táirge freisin ceanglais a leagtar amach i reachtaíocht eile an Aontais um chomhchuibhiú.
Airteagal 30 6.
Féadfaidh an Coimisiún, trí bhíthin gníomhartha tarmligthe, sonraíochtaí teicniúla a leagan síos le haghaidh lipéad, picteagram nó aon mharcanna eile a bhaineann le slándáil na dtáirgí ag a bhfuil eilimintí digiteacha, lena dtréimhsí tacaíochta mar aon le sásraí chun a n-úsáid a chur chun cinn agus chun feasacht phoiblí faoi shlándáil na dtáirgí ag a bhfuil eilimintí digiteacha a mhéadú. Agus dréachtghníomhartha cur chun feidhme á n-ullmhú aige, rachaidh an Coimisiún i gcomhairle le geallsealbhóirí ábhartha, agus, más rud é go bhfuil sé bunaithe cheana de bhun Airteagal 52(15), ADCO. Glacfar na gníomhartha cur chun feidhme sin i gcomhréir leis an nós imeachta scrúdúcháin dá dtagraítear in Airteagal 62(2).

1.1 Tagairtí

1.2 Ceanglais aitheanta

1.3 Caighdeáin ghaolmhara

2. Ceanglais aitheanta

Ceanglais

3. Caighdeáin ghaolmhara

Caighdeáin
SCF Product Management

Description

Mechanisms exist to design and implement product management processes to proactively govern the design, development and production of Technology Assets, Applications and/or Services (TAAS) across the System Development Life Cycle (SDLC) to:
(1) Improve functionality;
(2) Enhance security and resiliency capabilities;
(3) Correct security deficiencies; and
(4) Conform with applicable statutory, regulatory and/or contractual obligations.

Possible Solutions & Considerations

Micro-Small Business (<10 staff) / BLS Firm Size Classes 1-2

∙ Defined business processes
∙ Product / project management
∙ Defined technical requirements
∙ Defined business requirements

Small Business (10-49 staff) / BLS Firm Size Classes 3-4

∙ Defined business processes
∙ Product / project management
∙ Defined technical requirements
∙ Defined business requirements

Medium Business (50-249 staff) / BLS Firm Size Classes 5-6

∙ Defined business processes
∙ Product / project management
∙ Defined technical requirements
∙ Defined business requirements
∙ System Development Lifecycle (SDLC) governance / oversight

Large Business (250-999 staff) / BLS Firm Size Classes 7-8

∙ Defined business processes
∙ Product / project management
∙ Defined technical requirements
∙ Defined business requirements
∙ System Development Lifecycle (SDLC) governance / oversight

Enterprise (> 1,000 staff) / BLS Firm Size Class 9

∙ Defined business processes
∙ Product / project management
∙ Defined technical requirements
∙ Defined business requirements
∙ System Development Lifecycle (SDLC) governance / oversight

SCR-CMM

Level 0 Not Performed

Practices are non-existent, based on the inability to demonstrate an implemented and operational capability. A reasonable person would conclude the control is not being performed.

Level 1 Performed Informally

Technology Development & Acquisition (TDA) domain capabilities are ad hoc and inconsistent. Capability criteria associated with this control may include:
▪ Policies, standards & procedures associated with TDA domain capabilities provide limited coverage due to the depth and breadth of the existing documentation.
▪ Technology development & acquisition-related activities are decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.
▪ Secure development practices loosely conform to industry-recognized standards for secure engineering (e.g., OWASP, NIST SP 800-218 and NIST SP 800-160).
▪ IT and/or cybersecurity personnel use an informal process to govern changes to the software library to prevent unauthorized changes and create an audit trail of changes made.

Level 2 Planned Tracked

Technology Development & Acquisition (TDA) capabilities are requirements-driven, but are not standardized across the entity (e.g., local/regional level consistency). Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Policies and standards associated with TDA domain capabilities are formally documented and centrally-managed by the entity.
▪ Standardized Operating Procedures (SOP) associated with TDA domain capabilities are documented and maintained by process owners.
▪ IT and/or cybersecurity personnel work with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with TDA domain capabilities to address applicable statutory, regulatory and/or contractual requirements for Technology Assets, Applications, Services and/or Data (TAASD).
▪ Technology development and acquisition-related controls are primarily administrative and preventative in nature (e.g., policies, standards and procedures & guidelines).
▪ Technology development and acquisition management may be a defined function (e.g., team or department) or assigned as an additional duty to existing IT and/or cybersecurity personnel.
▪ Secure development practices mostly conform to industry-recognized standards for secure engineering of Technology Assets, Applications and/or Services (TAAS) (e.g., OWASP, NIST SP 800-218 and NIST SP 800-160).
▪ An application development team, or similar function, uses a structured process to design, build and maintain secure configurations for test, development, staging and production environments.
▪ Development and acquisition management is decentralized (e.g., a localized/regionalized function) and uses non-standardized methods to implement secure, resilient and compliant practices.

Level 3 Well Defined

Technology Development & Acquisition (TDA) capabilities are standardized across the entity for applicability to People, Processes, Technologies, Data and/or Facilities (PPTDF) to ensure consistency for Technology Assets, Applications, Services and/or Data (TAASD). Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Policies and standards associated with TDA domain capabilities are formally documented and centrally-managed by the entity's Governance, Risk & Compliance (GRC) team, or similar function.
▪ Standardized Operating Procedures (SOP) associated with TDA domain capabilities are well-documented and kept current by process owners.
▪ A software development team, or similar function, is appropriately staffed and supported to implement and maintain TDA domain capabilities.
▪ Technology is leveraged to enhance the efficiency and accuracy of technology development and acquisition management (e.g., project management software, software escrow solution and software testing tools).
▪ The entity's Governance, Risk & Compliance (GRC) team, or similar function, works with business stakeholders and process owners to appropriately scope and reasonably implement cybersecurity and data protection controls associated with TDA domain capabilities to address Minimum Compliance Requirements (MCR) (e.g., applicable statutory, regulatory and/or contractual requirements) and Discretionary Security Requirements (DSR) (e.g., entity-required controls).
▪ An implemented and operational capability exists to design and implement product management processes to proactively govern the design, development and production of Technology Assets, Applications and/or Services (TAAS) across the System Development Life Cycle (SDLC) to:
(1) Improve functionality;
(2) Enhance security and resiliency capabilities;
(3) Correct security deficiencies; and
(4) Conform with applicable statutory, regulatory and/or contractual obligations.

Level 4 Quantitatively Controlled

Technology Development & Acquisition (TDA) capabilities, in addition to being standardized across the entity and centrally managed to ensure consistency across Technology Assets, Applications, Services and/or Data (TAASD), efforts are metrics driven to provide sufficient insight for decision makers to predict optimal performance, ensure continued operations and/or identify areas for improvement. Capability criteria associated with this control reasonably expect the following criteria to exist:
▪ Applicable SCR-CMM Level 3 (Well Defined) capabilities are implemented and operational.
▪ Metrics reporting includes quantitative analysis of Key Performance Indicators (KPIs).
▪ Metrics reporting includes quantitative analysis of Key Risk Indicators (KRIs).
▪ Scope of metrics, KPIs and KRIs covers organization-wide cybersecurity and data protection controls, including functions performed by third-parties.
▪ Organizational leadership maintains a formal process to objectively review and respond to metrics, KPIs and KRIs (e.g., monthly or quarterly review).
▪ Based on metrics analysis, process improvement recommendations are submitted for review and are handled in accordance with change control processes.
▪ Business and technical stakeholders are involved in reviewing and approving proposed changes to evolve capabilities.

Level 5 Continuously Improving

Utilize SCR-CMM Level 3 or Level 4 (if available) criteria definitions:
▪ There are no defined Level 5 criteria, since it is reasonable to assume a continuously-improving process is not necessary to operationalize this control.
▪ Level 5 capabilities should be considered “world-class” where the control builds on Level 4 capabilities, but are continuously improving through Artificial Intelligence (AI) and/or Machine Learning (ML) technologies.
▪ While it may be possible to develop responsive capabilities for this control through the use of AI and/or ML technologies, the criteria would be organization-specific to define.