Framaforms

Créez rapidement et simplement des formulaires en ligne

Shaping CRA compliance for SMEs with OCCTET project

Début : 1 / 2

Introduction

This survey is conducted as part of the OCCTET Project (Open CyberSecurity Compliance Toolkit), an EU-funded initiative aimed at helping Small and Medium Enterprises (SMEs) comply with the Cyber Resilience Act (CRA). The OCCTET project develops open-source tools and resources to streamline compliance with cybersecurity requirements for Free and Open Source Software (FOSS) used in digital products.

Learn more about the OCCTET project: https://occtet.eu/

The CRA establishes cybersecurity requirements for products with digital elements, including software and hardware. This survey aims to identify the challenges and needs of SMEs in achieving compliance. Your responses will directly contribute to the development of practical tools and resources to support SMEs in navigating these regulations.

By participating, you will:

  • Learn about CRA requirements.
  • Prepare for compliance.
  • Be the first to access OCCTET tools.
  • Reduce cost (cost saving through the adoption of open-source tools, reduction in manual effort for compliance documentation and assessment).

Participation is free, and the results of the OCCTET project are licensed as open source.

DISCLAIMER:

Your responses will be used solely for research and analysis purposes to develop tools and resources supporting SME compliance with the CRA. All responses will be handled in compliance with the privacy policies of the Eclipse Foundation and the OCCTET project. No personal or identifiable information will be shared.

Section 1: Participant Information

CRA requirements can vary based on the size and resources of an organization.
Products with digital elements include IoT devices, software applications, or embedded systems. This question helps determine CRA applicability.
Products with digital elements include IoT devices, software applications, or embedded systems. This question helps determine CRA applicability.
(Examples: Healthcare, Manufacturing, Retail, IT Services, IoT Development) Different sectors may face unique cybersecurity challenges.

Section 2: Awareness and Readiness for CRA

This helps us understand resource allocation for compliance efforts.
This helps us understand resource allocation for compliance efforts.

Section 3: Secure Product Design (CRA Article 8)

CRA Article 8 requires integrating security measures into the design and development of products.
(secure coding guidelines, threat modeling, code review tools, automated vulnerability scanning.)

Section 4: Lifecycle Management (CRA Article 10)

CRA Article 10 requires manufacturers to manage product cybersecurity throughout its lifecycle, including vulnerability handling, regular updates, and notifying users of critical security issues.

(Examples: Lack of automated tools, limited resources, challenges in coordinating updates with end users.)

Section 5: Documentation and Transparency (CRA Article 10(3))

The CRA mandates manufacturers to provide clear documentation to users about the cybersecurity aspects of a product, including instructions for secure use and details about the product’s security support period.

(Examples: Limited technical writing expertise, unclear regulatory requirements, lack of templates.)

Section 6: Use of Open-Source Tools

Many SMEs use Free and Open Source Software (FOSS) tools to manage vulnerabilities, generate SBOMs, or streamline compliance. The CRA applies to such tools if integrated into a product with digital elements.

(Examples: SBOM generators, vulnerability scanners, dependency tracking tools, secure coding libraries.)
(Examples: Rapid updates, lack of documentation, complex dependency management.)

Section 8: Recommendations

(Examples: Automated vulnerability tracking tools, simplified templates for compliance documentation, training on secure development practices.)
(Examples: Financial support, free tools, compliance consulting, sample templates.)

Contacter l'auteur⋅rice de ce formulaire

Pour contacter l'auteur⋅rice de ce formulaire, cliquez ici


Ne communiquez aucun mot de passe via Framaforms.