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).
Related Semiconductor IP
- RISC-V CPU IP
- AES GCM IP Core
- High Speed Ethernet Quad 10G to 100G PCS
- High Speed Ethernet Gen-2 Quad 100G PCS IP
- High Speed Ethernet 4/2/1-Lane 100G PCS
Related Blogs
- Verifying Processor Security, Part 2
- EDA Carnivores, part 2: Apache acquires Sequence Design
- ST-Ericsson (Part 2): Diverse Offering
- Intel vs. ARM: In the Smartphone Era (Part 2)
Latest Blogs
- Why Choose Hard IP for Embedded FPGA in Aerospace and Defense Applications
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- Quintauris: Accelerating RISC-V Innovation for next-gen Hardware
- Say Goodbye to Limits and Hello to Freedom of Scalability in the MIPS P8700
- Why is Hard IP a Better Solution for Embedded FPGA (eFPGA) Technology?