EU Cyber Resilience Act (CRA)
EU Cyber Resilience Act (CRA) とは何ですか?
EU Cyber Resilience Act (CRA)EU Regulation 2024/2847 imposing security-by-design, vulnerability handling, and conformity-assessment obligations on essentially all products with digital elements sold in the EU, with main obligations applying from December 2027.
The EU Cyber Resilience Act (Regulation 2024/2847) is the first horizontal EU cybersecurity law applying to products. It entered into force in December 2024 with a phased timeline: vulnerability-reporting obligations from September 2026 and the full set of essential requirements from 11 December 2027. The CRA covers 'products with digital elements' — software, hardware, or both, including IoT devices, libraries, and many SaaS-tied products — placed on the EU market. Manufacturers must perform a cybersecurity risk assessment, deliver products free of known exploitable vulnerabilities, ship secure-by-default configurations, support security updates for at least five years (or product life if shorter), maintain an SBOM, handle vulnerabilities including coordinated disclosure, and report actively exploited vulnerabilities and severe incidents to ENISA within 24 hours. Open-source software is largely excluded from manufacturer obligations but introduces 'open-source software stewards' as a lighter category. Penalties reach €15 million or 2.5 % of worldwide annual turnover. The CRA is widely expected to reshape OSS funding, embedded device security, and vendor risk programs through the late 2020s.
● 例
- 01
An IoT camera manufacturer issues a CRA-mandated 24-hour ENISA notification when an actively exploited bug is reported on its firmware.
- 02
A SaaS vendor adds a 5-year security-update commitment and a CycloneDX SBOM to its product documentation to align with CRA essential requirements.
● よくある質問
EU Cyber Resilience Act (CRA) とは何ですか?
EU Regulation 2024/2847 imposing security-by-design, vulnerability handling, and conformity-assessment obligations on essentially all products with digital elements sold in the EU, with main obligations applying from December 2027. サイバーセキュリティの コンプライアンスとフレームワーク カテゴリに属します。
EU Cyber Resilience Act (CRA) とはどういう意味ですか?
EU Regulation 2024/2847 imposing security-by-design, vulnerability handling, and conformity-assessment obligations on essentially all products with digital elements sold in the EU, with main obligations applying from December 2027.
EU Cyber Resilience Act (CRA) はどのように機能しますか?
The EU Cyber Resilience Act (Regulation 2024/2847) is the first horizontal EU cybersecurity law applying to products. It entered into force in December 2024 with a phased timeline: vulnerability-reporting obligations from September 2026 and the full set of essential requirements from 11 December 2027. The CRA covers 'products with digital elements' — software, hardware, or both, including IoT devices, libraries, and many SaaS-tied products — placed on the EU market. Manufacturers must perform a cybersecurity risk assessment, deliver products free of known exploitable vulnerabilities, ship secure-by-default configurations, support security updates for at least five years (or product life if shorter), maintain an SBOM, handle vulnerabilities including coordinated disclosure, and report actively exploited vulnerabilities and severe incidents to ENISA within 24 hours. Open-source software is largely excluded from manufacturer obligations but introduces 'open-source software stewards' as a lighter category. Penalties reach €15 million or 2.5 % of worldwide annual turnover. The CRA is widely expected to reshape OSS funding, embedded device security, and vendor risk programs through the late 2020s.
EU Cyber Resilience Act (CRA) からどのように防御しますか?
EU Cyber Resilience Act (CRA) に対する防御は通常、上記の定義で述べたとおり、技術的統制と運用上の実践を組み合わせます。
EU Cyber Resilience Act (CRA) の別名は何ですか?
一般的な別名: CRA, Regulation EU 2024/2847。
● 関連用語
- compliance№ 816
NIS2 指令
EU 域内の重要事業者および基幹事業者に対し、サイバーセキュリティの基本要件とインシデント報告義務を引き上げる EU 指令 2022/2555。
- compliance№ 387
DORA
金融セクター向けデジタル運用レジリエンスに関する EU 規則 2022/2554。2025 年 1 月 17 日から適用。
- compliance№ 620
ISO/IEC 27001
情報セキュリティマネジメントシステム(ISMS)の要求事項を定める国際規格で、組織は正式な認証を取得できる。
- appsec№ 1185
ソフトウェア部品表(SBOM)
ソフトウェアを構成するコンポーネント・ライブラリ・依存関係を、バージョンや関係とともに機械可読な形で正式に列挙したインベントリ。
- attacks№ 244
協調的脆弱性開示 (CVD)
発見者・影響を受けるベンダー、必要に応じて調整役が、脆弱性の公開時期について合意したうえで開示を行うプロセス。
- appsec№ 1094
セキュアコーディング
防御的パターン・言語固有のルール・公認ガイドラインに従い、セキュリティ欠陥を最小化するようにソースコードを書く実践。