I’m evaluating Cryptography Bill of Materials (CBOM) concepts (CycloneDX) for organizational use.
SonarQube has the SonarCryptography plugin, which detects cryptographic usage such as algorithms, key sizes, modes, and insecure crypto patterns.
I would like to clarify a few points:
-
Ownership / origin
-
Is the SonarCryptography plugin developed and maintained by SonarSource, or
-
Is it originated or backed by IBM research (since CBOM work is often associated with IBM and the CycloneDX CBOM initiative)?
-
-
Intended usage
-
Is the plugin primarily meant for code quality / security detection, or
-
Is it considered suitable as a data source for CBOM generation?
-
-
CBOM alignment
-
Can the findings from SonarCryptography reasonably be mapped to a CycloneDX CBOM, or
-
Is that outside the intended scope of the plugin?
-
Looking for clarification on the design intent and recommended usage, especially in CBOM discussion