CodeArts Governance
CodeArts Governance
- Service Overview
- Billing
- Getting Started
- User Guide
- Best Practices
-
FAQs
-
Binary Software Composition Analysis (SCA)
- What Objects Can Be Scanned?
- What Are the Precautions of Binary SCA?
- How Does Binary SCA Work and What Risks Can be Identified?
- How Do I Handle Open-Source Software Vulnerabilities?
- How Do I Handle Secure Complier Option Vulnerabilities?
- How Do I Handle Security Configuration Issues?
- How Do I Handle Information Leakage Risks?
- Why Is the Component Version Not Identified or Incorrectly Identified?
- Why Can't I Buy a CodeArts Governance Package?
- How Do I View the Path of a File that Has Vulnerabilities?
- What Can I Do If a Binary SCA Task Fails?
- How Do I Check User Group Permissions and Grant Permissions?
- What Should I Do If a Role Permission Error (Roles with READONLY_USER) Is Reported?
-
Binary Software Composition Analysis (SCA)
- General Reference
On this page
Copied.
Querying Audit Logs
Cloud Trace Service (CTS) records operations on CodeArts Governance for query, audit, and backtrack.
Operations Recorded by CTS
Operation |
Resource Type |
Event Name |
---|---|---|
Creating a binary SCA job |
task |
createScaTask |
Deleting a binary SCA job |
task |
deleteScaTask |
Generating a binary SCA report |
task |
exportPdfScaTask/exportExcelScaTask |
Cleaning resources for a binary SCA job |
resource |
cleanUpScaResources |
Checking Audit Logs
Query CodeArts Governance traces on the CTS console. For details, see Querying Real-Time Traces.
Feedback
Was this page helpful?
Provide feedbackThank 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.
For any further questions, feel free to contact us through the chatbot.
Chatbot