KhronosGroup / KhronosGroup/KSCAF_DocGuidelines
Cybersecurity Assurance Program (UL CAP)
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
UL’s 2900-1 tests measure application security, information access control via authentication processes, engineer mode hacking protection and software falsification protection. Additional information on UL 2900-1 standards can be found at https://goo.gl/iJrf90.
UL Cybersecurity Assurance Program (CAP)
Securing Software in Physical Devices
The UL Cybersecurity Assurance Program (UL CAP) is an independent third-party testing and certification program through UL specific to network-connectable products and software components. It includes industrial control systems (ICS), medical devices, in-vehicle software systems and other IoT devices.
Cybersecurity National Action Plan (CNAP)
Department of Homeland Security enlisted UL and other industry partners to develop a Cybersecurity Assurance Program to test and certify networked devices within the Internet of Things.
New UL2900 Certification
This new certification program verifies product compliance with UL2900, a series of standards developed by UL with input from industry stakeholders, including Synopsys. UL2900 validates that a product offers a reasonable level of protection against cybersecurity risks that may result in unintended or unauthorized access, change or disruption.
It may be it is relevant to mention this and investigate further.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue text and review the linked UL 2900-1 information to determine whether UL CAP is relevant to these safety-critical technology guidelines. The issue does not name a file, test, or entry point; done would require a decided scope and a clear documentation location or an explicit reason not to include it.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100