Help Center/ CodeArts Governance/ FAQs/ Binary Software Composition Analysis (SCA)/ How Does Binary SCA Work and What Risks Can be Identified?

Updated on 2025-06-05 GMT+08:00

View PDF

How Does Binary SCA Work and What Risks Can be Identified?

CodeArts Governance decompresses and scans your software packages and firmware. It performs component feature analysis based on the bill of materials (BOM) to identify possible rule violations. The following lists the vulnerabilities that can be identified.

Open source software's known vulnerabilities and license compliance risks.
Security configuration risks in hard-coded credentials, sensitive files (keys, certificate, and debugging tools), OS authentication, and access control.
Disclosure risks of IP addresses, hard-coded keys, passwords, and Git/SVN repositories.
Compiler security option risks in binary program compilation.
Figure 1 Risk items

Parent topic: Binary Software Composition Analysis (SCA)

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.