Belarus Jenkins Meetup - Managing security in Jenkins with configuration-as-code and roles

Managing security in Jenkins with
Configuration-as-Code and roles
Oleg Nenashev
CloudBees, Inc.
Belarus Jenkins Meetup
Minsk, July 29, 2017

@oleg_nenashev, #jenkinsBY © 2017 CloudBees, Inc. All Rights Reserved. 2
About me
@oleg_nenashev
oleg-nenashev
LibreCores
project
St. Petersburg
Polytechnic University
Jenkins meetups

Oleg’s
“Hall of
Shame”(c)
• Plugins
• Jenkins Core
• Windows Service
Wrapper
• Remoting
• Security

About you

Agenda
•Introduction to Jenkins Security
•System Configuration-as-Code in Jenkins
•Ownership-based security
•Live Demos
Disclaimer:
• Presentation represent the author’s personal opinion
• Author’s personal opinion may differ from official
positions of CloudBees and/or Jenkins community
• Many Jenkins instances were harmed, use carefully

1. Most popular CI/CD tool in the world
2. Generic automation server
3. Flexible and extensible
4. It’s open source, big community
5. Commercial support vendors
6. …
Who is Mr. Jenkins?
https://jenkins.io

Jenkins is a…
remote execution engine
(by design)

Jenkins is a…
remote execution engine
(by design)
• One can run code and system commands
• Access to master system
• Access to agents
• Access to private/public clouds

Jenkins…
has access to sensitive data
(by design)

Jenkins…
has access to sensitive data
(by design)
• Credentials
• Private repositories
• Artifacts, including release ones

Jenkins is a…
service
(by design)

Jenkins is a…
service
(by design)
• Multiple users
• Different expertise
• Users may misuse permissions

What does security mean?
Jenkins security
Intrusion and data
theft protection
Restrictions within
organization

Jenkins security
Intrusion and data
theft protection
Restrictions within
organization
• Must-have in internet-facing instances
• Paranoid mode is fine

Jenkins security
Intrusion and data
theft protection
Restrictions within
organization
• Better user experience
• Protection from unintentional actions
• Protection from lack of expertise

Protecting Jenkins instance.
Basic Rules

•Limited number of admins
•Permissions
•Security audit
Rule #0. Use security!

• Security Team
• Fixes in Jenkins core and Plugins
• https://jenkins.io/security/
Jenkins
Board
Core
Team
Security
LTS
Events
INFRA
Website

Rule #1. Keep Updating
• Frequent security releases
• Weekly
• Current LTS baseline
• Info sources
• https://jenkins.io/security/advisories/
• jenkinsci-advisories mailing list
(including announcements)
• RSS feed
2.46.2
Exploits
are in
the wild,
update
ASAP

•Not enough?
LTS is only 3 months…

•Not enough?
•Build your own core (custom fork)
•HINT: Join the security team to get info about
changes in advance

•Not enough?
•Build your own core (custom fork)
•Use custom versions from vendors:
• https://wiki.jenkins-ci.org/display/JENKINS/Commercial+Support
• CloudBees Jenkins Enterprise

Do you pull latest images
from DockerHub?

•What’s inside?
•Who can change them?
•What if there is a malicious code?
from DockerHub?

•What’s inside?
•Who can change them?
•What if there is a malicious code?
•How is it different from other package sources?
from DockerHub?

Rule #2. Know what you use
Monitor plugin versions and release notes
• Beware of transient dependencies (!)
• Also monitor JIRA
Consider using locally managed sources
• Internal Maven
• Docker Registry
• Custom Jenkins Update Center: Juseppe
• https://github.com/yandex-qatools/juseppe
Use static configurations
• Configuration-as-Code

Configuration as Code in Jenkins
JobsSystem
Configurations

System Configurations… as Code
External tools
Jenkins CLI
and REST
API
python-
jenkins
jenkins-client
(java)
Configuration
Management
Ansible, Chef,
…
Docker,
Docker
Compose
...
Solutions in
Jenkins
Groovy Boot
Hooks
System
Config DSL
(alpha)
Scriptler
Plugin
SCM Sync
Configuration UnstableJust examples…
Insecure

Groovy Hooks
• Universal solution
• Hooks on startup events
• init, boot-failure
• Scripts
• WEB-INF/HOOK.groovy in jenkins.war
• WEB-INF/HOOK.groovy.d/*.groovy in jenkins.war
• $JENKINS_HOME/HOOK.groovy
• $JENKINS_HOME/HOOK.groovy.d/*.groovy in lexical order
https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Hook+Script

https://hub.docker.com/r/onenashev/
demo-jenkins-config-as-code/
Groovy Hooks

Rule #3. Keep Jenkins in a sandbox
Do not run masters/agents under
system accounts
Restrict access to non-required
resources
• Generic accounts
• Read-only repositories
Sandbox your scripts as well

Scryptocalypse
https://jenkins.io/security/advisory/2017-04-10/
• Unlimited scripting
• More than 30 plugins affected
•Groovy Plugin
•JobDSL Plugin
•Grails Plugin
•Scriptler Plugin
• Some of them are blocked

DIY

Jenkins Script
Security
https://plugins.jenkins.io/
script-security
DIY

Script Security Plugin
Used in [almost] all
Groovy plugins
https://plugins.jenkins.io/script-security

Is it enough to
become secure?

Rule #4. Do not Run Jobs on master
• Builds have access to the master filesystem
• They can…
• Read data from other builds/artifacts
• Read secret hashes
• Modify Jenkins system configuration
• …
• You don’t want that

• Solution 1:
• Set “0” executors on master
• Another node running under different account
• BUT: Does not protect from fly-weight tasks

• Solution 1:
• 0 executors on master
• Another node running under different account
• BUT: Does not protect from fly-weight tasks
• Solution 2:
• Job Restrictions Plugin
• Details: later

•By default builds run with the System account
•Users may trigger wrong builds
•Users can extract data
Rule #5. Do not trust your builds

Authorize Project Plugin
Authorize builds
• Global default
• Whitelist of user-
configurable
strategies
• Job properties
https://plugins.jenkins.io/authorize-project

•Audit Trail – logging of actions
•https://plugins.jenkins.io/audit-trail
•Security Inspector – permission checks
•https://plugins.jenkins.io/security-inspector
•…
Rule #6. Audit your security

Security Inspector Plugin
https://plugins.jenkins.io/security-inspector
Reports for jobs, agents and users

•Assign leads to jobs and agents
•Share the maintenance effort with them
•Make the ownership explicit
Rule #7. Make the responsibilities explicit

Common strategies do not “just work”
Project Matrix Authorization Strategy
• Hard to manage
• No support of Node permissions
Role-Based Strategy
• Regular expression for each role
• Performance: Hundreds of Regex checks every request
• Web UI easily hangs

Ownership-based Security
Role-
Strategy
Ownership
Job
Restrictions
• Assign owners of jobs/nodes
• Fancy UI
• Auth strategy
• Macro engine
• Restrict runs for
jobs and nodes
http://bit.ly/ownership-based-security
+ Authorize Project

Ownership Plugin
• Primary and Secondary Owners
• Summary Boxes, View filters, etc.
• Environment variables
• Integration with Security plugins Customizable layout
https://plugins.jenkins.io/ownership

Ownership Info. Definition and Inheritance
Folders
Jobs
Nodes
Runs
Sub-
Projects

Demo. What’s inside?
Ownership
0.10.0
Job Restrictions
0.6
Security Inspector
0.4
Jenkins core
2.62.2
(minimal – 1.625)
Authorize Project
1.3.0
Dynamic Search View
0.2.2
Role Strategy
2.5.1

https://hub.docker.com/r/onenashev/
demo-jenkins-config-as-code/

Setting ownership info

Ownership Info. What Do you get?
• Ownership Summary Boxes
• Ownership View Columns
• View Filters
• Also: @Me macro
Customizable layout

Example: Quick administration contacts
Customizable template

Ownership-Based Security. Role-Based Strategy Settings
Roles
[1/2]

Roles
[2/2]

Assignments

Jobs. Securing access
Untrusted secondary owners!

Jobs. Authorize Project
Jobs get
authenticated as
owners =>
• Permissions
• Node access
(Computer.BUILD)

Using Data in Jobs. Freestyle

Using Data in Jobs. Pipeline

Jenkins nodes
• Similar Ownership
Management
• Special permission
• Node Ownership Monitor
• => info in the table

Securing Nodes

Job Restrictions. Protecting the Master node
• NEVER let users run
jobs on master
• Only use it for system
jobs owned by admins

Ownership-Based Security: Links
Plugins:
• https://plugins.jenkins.io/ownership
• https://plugins.jenkins.io/role-strategy
• https://plugins.jenkins.io/job-restrictions
• https://plugins.jenkins.io/authorize-project
Ownership-based security:
• http://bit.ly/ownership-based-security
Demo
• https://github.com/oleg-nenashev/demo-jenkins-config-as-code

Ownership-Based Security: Out of the scope
• Item-specific security
•Plugging Matrix Project Security into Ownership Engine
• Ownership-based restrictions for triggering jobs
• Ownership assignment policy on create/copy
• Groovy API for System Scripts (needs some love)
• “sudo” mode implementation for admins

•Follow the security advisories
•Keep your Jenkins up to date
•Use Security plugins
Takeaways

•Many existing solutions for large-scale
•They are not well documented sometimes…
•But they exist
Rule #-1. Explore

•Security page: https://jenkins.io/security/
•Advisories: https://jenkins.io/security/advisories/
•Ownership-based security: http://bit.ly/ownership-based-security
•Demo: https://hub.docker.com/r/onenashev/demo-jenkins-
config-as-code/
Links

Thank you!
Contacts:
E-mail: onenashev@cloudbees.com
GitHub: oleg-nenashev
Twitter: @oleg_nenashev

Belarus Jenkins Meetup - Managing security in Jenkins with configuration-as-code and roles

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Belarus Jenkins Meetup - Managing security in Jenkins with configuration-as-code and roles

Semelhante a Belarus Jenkins Meetup - Managing security in Jenkins with configuration-as-code and roles (20)

Último

Último (20)

Belarus Jenkins Meetup - Managing security in Jenkins with configuration-as-code and roles