Skip to content

Adding new policies #328

@FotiosBistas

Description

@FotiosBistas

Hello,

I was wondering whether it would be possible to support additional compliance policies based on external regulatory or certification frameworks. For example, the ECCG Agreed Cryptographic Mechanisms v2 published by ENISA defines approved, deprecated, and non-recommended cryptographic algorithms and parameter requirements:

https://certification.enisa.europa.eu/document/download/a845662b-aee0-484e-9191-890c4cfa7aaa_en?filename=ECCG%20Agreed%20Cryptographic%20Mechanisms%20version%202.pdf

Given that the EU Cyber Resilience Act (CRA) may rely on European cybersecurity certification schemes and associated guidance (such as ECCG) when defining cryptographic expectations, support for such compliance profiles could become increasingly relevant for vendors operating in the EU market.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions