Security audit logging in Jenkins - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Jenkins audit log plugin output

You enabled the Jenkins Audit Trail plugin and configured it to log all user actions. What will be the output in the audit log file when a user named 'alice' triggers a build for job 'MyApp'?

A DEBUG: Job MyApp started by user alice

B ERROR: Build failed for job MyApp by alice

C INFO: User alice triggered build for job MyApp

D WARN: Unauthorized access attempt by alice on job MyApp

💡 Hint

Audit logs record user actions like triggering builds, not errors or warnings unless configured.

The Audit Trail plugin logs user actions such as triggering builds with INFO level messages. Errors or warnings are not part of audit logs unless an error occurs.

❓ Configuration

intermediate

Configuring Jenkins audit logging to file

Which configuration snippet correctly enables audit logging to a file named 'audit.log' in Jenkins?

A auditTrail { enabled yes; logFile 'audit.log' }

B auditTrail { enabled true; logFile 'audit.log' }

C auditTrail { enable true; file 'audit.log' }

D auditTrail { enabled true; logFile '/var/log/jenkins/audit.log' }

💡 Hint

The correct syntax uses 'enabled true' and an absolute path for logFile.

The Audit Trail plugin configuration requires 'enabled true' and a valid absolute path for the logFile parameter.

❓ Troubleshoot

advanced

Audit logs missing user info

After enabling audit logging, you notice the logs do not show which user performed actions. What is the most likely cause?

A Audit Trail plugin is disabled

B Audit Trail plugin is enabled but Jenkins security realm is set to 'None'

C Jenkins master node is offline

D Audit logs are rotated too frequently

💡 Hint

User info depends on Jenkins authentication being active.

If Jenkins security realm is 'None', no user authentication exists, so audit logs cannot record user info.

✅ Best Practice

advanced

Best practice for securing Jenkins audit logs

Which practice best secures Jenkins audit logs against unauthorized access?

A Store audit logs on a separate secured server with restricted access

B Keep audit logs on the Jenkins master with default permissions

C Allow all Jenkins users to read audit logs for transparency

D Disable audit logging to avoid sensitive data exposure

💡 Hint

Audit logs contain sensitive info and should be protected carefully.

Storing audit logs on a separate secured server with restricted access prevents tampering and unauthorized viewing.

🔀 Workflow

expert

Implementing centralized audit logging for Jenkins

You want to send Jenkins audit logs to a centralized syslog server for compliance. Which sequence of steps is correct?

A 1,2,4,3

B 2,1,3,4

C 1,4,2,3

D 4,1,2,3

💡 Hint

Start with local logging, then forwarding, secure the channel, then verify.

First configure local audit logging, then forward logs via syslog agent, secure the channel, and finally verify logs arrive.