Audit logs
Audit logs
Audit logs provide a comprehensive history of actions and events within Jit, enabling better tracking, compliance, and insights into key activities. These logs are particularly valuable for administrators managing security and operational events.
Supported Audits
Jit logs the following activities for auditing. All activities will be audited with the username and email, or the Source Code Manager identity.
Action | Details | Example |
---|---|---|
Findings ignored from backlog | Logs ignored findings from backlog page. The description holds the number of findings, reason, comment and a unique identifier of the action. | User: [email protected] Description: 2 findings ignored, Reason: 'false_positive', Comment: 'Not relevant findings', Ignore rule ID: 'd495a58f-7d4c-48e4-a4e4-30f781fbe150' |
Findings ignored from PR | Logs ignored findings from PR/MR. The User will be displayed as "<Github/Gitlab username> (scm)" The description holds the number of findings, reason, comment and a unique identifier of the action. | User: jitgithubaccount (scm) Description: 2 findings ignored, Reason: 'false_positive', Comment: '#jit_ignore_fp', Ignore rule ID: 'd495a58f-7d4c-48e4-a4e4-30f781fbe150' |
Export Security Plan results | Logs the action of exporting specific Security Plan results. The description will contain the name of the Security Plan. | Description: Export Plan OWASP Application Security Verification Standard (ASVS) results |
Ticket created | Logs the action of creating tickets in the ticketing system from the UI. Supported ticketing systems: Jira, monday.com, LinearB, and more. | Description: Ticket 10323 created. URL: '<https://jit-jira.atlassian.net/browse/KAN-67/10323'> |
Export <artifact> | Logs the action of exporting an artifact trough the platform / API. Most commonly - exporting an SBOM report. | Action: Export SBOM Description: Artifact was exported. ID: '01JE19R1NNYJ7JW9VJGZCD13S9' |
Export <artifact> failed | Logs the action of an attempt to export an artifact, but the attempt was block, most likely because this feature is not opened for the customer (As this is a premium feature). | Action: Export SBOM failure Description: Failure exporting artifact. ID: '01JE19R1NNYJ7JW9VJGZCD13S9', Reason: FORBIDDEN |
User logged in | Logs the action of logging in to the platform. | Description: User logged in to the application |
Removed user <user> from account | Logs the action of removing a user from the platform, an activity done by an admin via Users & settings. | Description: Removed access from the account for user [email protected] |
Assigned roles | Logs the action of assigning roles to a user. | Description: Assigned 1 roles for user [email protected] : Engineering Manager |
Removed roles | Logs the action of removing roles from a user. | Description: Removed roles for user [email protected] : Engineering Manager |
Added user | Logs the action of a user joining through an invitation link. This action will be logged as "System". | User: System Description: Added user [email protected] to tenant |
Created API key | Logs the action of creating a Tenant wide API key in the platform, to be used with Jit's public apis. | Description: Created new API key on the product |
Deleted API key | Logs the action of deleting an API key from Jit's platform. | Description: Deleted API key from the product |
Updated profile | Logs when Jit updates metadata for the user. For example - an indication when a user arrives from our vscode extension. | Description: User updated profile details |
Retention and Export
Audit logs are retained for 3 months.
Logs can be downloaded as a CSV file for offline analysis, archival, or sharing.
Accessing Audit Logs
Audit logs are available for administrators and can be accessed via Settings -> Users & Permissions -> Audit logs
Filtering and searching
Use free-text filtering to pinpoint specific events or actions efficiently such as emails, actions, etc.
Each column supports filtering as well, by clicking the icon above each field.
Updated 10 days ago