Upcoming IoT Security Legislation: Vulnerability Disclosure - Part 2
In part one of this two part series of blogs, Crypto Quantique discussed the PSTI Act, one of the requirements of which for IoT device manufacturers is to implement a means to receive reports of issues. The industry term for this is Vulnerability Disclosure.
Read part one of this blog here
What is Vulnerability Disclosure?
The European Union Agency for Cybersecurity (ENISA) defines vulnerability disclosure as “The process of identifying, reporting and patching weaknesses of software, hardware or services that can be exploited”. The idea is that security researchers find vulnerabilities in an organisation’s hardware or software and have a dedicated channel through which they can report their findings to that organisation. Coordinated vulnerability disclosure (CVD) is the industry recommended best-practice implementation of this, and is where the researcher works with the vendor or a coordinator intermediary to rectify the problem they have identified.
Why is CVD important?
To understand why vulnerability disclosure is important, it is first necessary to understand what a vulnerability is. A vulnerability is described by ETSI as a security bug or defect in a system, product or service; when an exploit takes place it is done so by taking advantage of one or more vulnerability. Vulnerability disclosure is a method by which organisations can, outside of regular security testing, become aware of vulnerabilities in its systems. In recent years vulnerability disclosure has received great attention from industry and now governments, with vulnerability disclosure being a requirement of both the UK’s PSTI Act and the EU Cyber Resilience Act (CRA).
To read the full article, click here
Related Semiconductor IP
- MACsec Engine optimized for 10Base-T1S/T1L applications
- Dual Port, Voltage Scaling Register File Compiler on GF22FDX+
- Single Port, Voltage Scaling, High Speed SRAM Memory Compiler on GF22FDX+
- I3C Full Controller / Target
- I3C HCI Host Controller
Related Blogs
- PCI Express Security and TEE Integration, Part 2 - Protecting PCIe Traffic
- Verifying Processor Security, Part 2
- Protecting Edge AI with RISC-V CHERI: See how easily memory-safe security can be added to an AI application (part 1)
- PCI Express Security and TEE Integration, Part 1 - Establishing Trust