Security audit logging in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable audit logging in Jenkins.

Jenkins

auditLogger = Jenkins.instance.getExtensionList('hudson.security.AuditLogger')[[1]]

Drag options to blanks, or click blank then click option'

A2

B1

C0

D-1

Attempts:

3 left

💡 Hint

Common Mistakes

Using index 1 or 2 causes an error because those indexes don't exist.

The audit logger is accessed by index 0 in the extension list.

2fill in blank

medium

Complete the code to enable audit logging for all authentication events.

Jenkins

auditLogger.setEnabled(true)
auditLogger.setLogAuthentication([1])

Drag options to blanks, or click blank then click option'

Atrue

Bundefined

Cnull

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using false disables logging, so no audit logs are created.

Setting logAuthentication to true enables logging of all authentication events.

3fill in blank

hard

Fix the error in the code to correctly log audit events to a file.

Jenkins

auditLogger.setLogFile(new File([1]))

Drag options to blanks, or click blank then click option'

A"/var/log/jenkins/audit.log"

B'/var/log/jenkins/audit.log'

C/var/log/jenkins/audit.log

D'var/log/jenkins/audit.log'

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting quotes causes syntax errors.

Using single quotes is valid but here double quotes are preferred.

The file path must be a string with quotes. Double quotes are correct here.

4fill in blank

hard

Fill both blanks to configure audit logging to include user and timestamp.

Jenkins

auditLogger.setFormat("User: [1], Time: [2]")

Drag options to blanks, or click blank then click option'

A%u

B%t

C%T

D%U

Attempts:

3 left

💡 Hint

Common Mistakes

Using %T or %U are incorrect format specifiers for user or time.

%u inserts the username, and %t inserts the timestamp in the log format.

5fill in blank

hard

Fill all three blanks to create a filter that logs only failed login attempts.

Jenkins

auditLogger.setFilter({ event -> event.getType() == [1] && event.getResult() == [2] && event.getUser() != [3] })

Drag options to blanks, or click blank then click option'

A"AUTHENTICATION"

B"FAILURE"

C"anonymous"

D"SUCCESS"

Attempts:

3 left

💡 Hint

Common Mistakes

Using "SUCCESS" instead of "FAILURE" logs successful logins, not failures.

This filter logs events where the type is AUTHENTICATION, the result is FAILURE, and the user is not anonymous.

Practice

1. What is the main purpose of security audit logging in Jenkins?

easy

A. To record important user and system actions for tracking and compliance

B. To speed up the build process

C. To automatically fix security vulnerabilities

D. To create backups of Jenkins configuration files

Solution

1. Step 1: Understand the role of audit logging

   Audit logging records actions taken by users and the system to keep a history of events.

2. Step 2: Identify the purpose in Jenkins context

   This helps track changes, investigate incidents, and meet compliance requirements.

3. Final Answer:

   To record important user and system actions for tracking and compliance -> Option A

4. Quick Check:

   Audit logging = record actions [OK]

Hint: Audit logs track actions for security and compliance [OK]

Common Mistakes:

• Confusing audit logs with build speed optimization
• Thinking audit logs fix security issues automatically
• Assuming audit logs create backups

2. Which Jenkins pipeline syntax correctly enables audit logging?

easy

A. pipeline { stages { auditLog() } }

B. pipeline { auditLog: true stages { ... } }

C. pipeline { options { auditLog() } stages { ... } }

D. pipeline { options { enableAudit() } stages { ... } }

Solution

1. Step 1: Recall correct syntax for enabling audit logging

   Audit logging is enabled inside the options block using auditLog().

2. Step 2: Check each option for syntax correctness

   pipeline { options { auditLog() } stages { ... } } uses correct syntax: options { auditLog() }. Others use invalid keys or wrong placement.

3. Final Answer:

   pipeline { options { auditLog() } stages { ... } } -> Option C

4. Quick Check:

   Enable auditLog() inside options [OK]

Hint: Use auditLog() inside options block in pipeline [OK]

Common Mistakes:

• Placing auditLog() outside options block
• Using incorrect option names like enableAudit()
• Setting auditLog as a key-value pair

3. Given this Jenkins pipeline snippet, what will be logged in the audit logs?

pipeline {
  options {
    auditLog()
  }
  stages {
    stage('Build') {
      steps {
        echo 'Building project'
      }
    }
  }
}

medium

A. Only the start and end of the pipeline execution

B. User actions and stage execution details including 'Build' stage

C. No logs because auditLog() is not a valid option

D. Only errors during the build stage

Solution

1. Step 1: Understand what auditLog() captures

   Audit logging records user actions and system events including stage executions.

2. Step 2: Analyze the pipeline snippet

   Since auditLog() is enabled, it logs the 'Build' stage execution and user actions triggering the pipeline.

3. Final Answer:

   User actions and stage execution details including 'Build' stage -> Option B

4. Quick Check:

   auditLog() logs user and stage events [OK]

Hint: auditLog() logs user and stage events in pipeline [OK]

Common Mistakes:

• Assuming auditLog() logs only errors
• Thinking auditLog() is invalid syntax
• Believing it logs only pipeline start and end

4. You added auditLog() in your Jenkins pipeline but no audit logs are generated. What is the most likely cause?

medium

A. Audit logs are only generated for freestyle jobs, not pipelines

B. The pipeline syntax is correct but auditLog() only logs errors

C. Audit logging requires a special user permission that is missing

D. The Jenkins audit logging plugin is not installed or enabled

Solution

1. Step 1: Check plugin requirement for audit logging

   Audit logging requires the Jenkins audit logging plugin to be installed and enabled.

2. Step 2: Evaluate other options

   AuditLog() logs all actions, not just errors; permissions affect access but not logging; pipelines support audit logging.

3. Final Answer:

   The Jenkins audit logging plugin is not installed or enabled -> Option D

4. Quick Check:

   Plugin must be installed for auditLog() to work [OK]

Hint: Ensure audit logging plugin is installed and active [OK]

Common Mistakes:

• Assuming auditLog() logs only errors
• Ignoring plugin installation requirement
• Thinking audit logging is disabled for pipelines

5. You want to audit log only changes made to Jenkins credentials. Which approach best achieves this?

hard

A. Configure audit logging plugin to filter and log only credential-related events

B. Add auditLog() in every pipeline that uses credentials

C. Manually check Jenkins logs for credential changes daily

D. Disable audit logging and rely on system backups

Solution

1. Step 1: Understand audit logging filtering capabilities

   The audit logging plugin can be configured to filter and log specific event types like credential changes.

2. Step 2: Compare options for effectiveness

   Adding auditLog() in pipelines logs all actions, manual checks are error-prone, and disabling logging loses audit data.

3. Final Answer:

   Configure audit logging plugin to filter and log only credential-related events -> Option A

4. Quick Check:

   Use plugin filters to target credential events [OK]

Hint: Use plugin filters to audit specific events like credentials [OK]

Common Mistakes:

• Logging all pipeline actions instead of filtering
• Relying on manual log checks
• Disabling audit logging to reduce noise