Rugged DevOps Will help you build ur cloudz

RUGGED DEVOPS WILL HELP
YOU BUILD UR CLOUDZ
by @wickett and @ernestmueller

OUTLINE
• Us, And Why You Care What We Say
• The Cloud, And How It Is Threatening You
• Rugged, And Its New Approach To Security
• DevOps, And How It Is Driving Collaborative Solutions
• Combining Cloud, Rugged, and DevOps To Solve The Problem
• How We Did Cloud Security With DevOps At NI
• Introducing RuggedDevOps Tool: Gauntlt

@wicke'
Senior
DevOps

Engineer

CISSP,
GWAPT,
CCSK,

GSEC,
GCFW

james@wicke'.me

@RuggedDevOps

theagileadmin.com

NI
CONFIDENTIAL

@ernestmueller

DevOps Platform Manager
and Release Manager,
Bazaarvoice

ernest.mueller@gmail.com

theagileadmin.com

THE GRAND UNIFIED THEORY
(ISP -> colo -> MSP) + virtualization
+ HPC + (AJAX + SOA -> REST APIs) =
IaaS
((web site -> web app) -> ASP) +
virtualization + fast ubiquitous
Internet + [RIA browsers && mobile] =
SaaS
IDE/4GLs + (EAI -> SOA) + SaaS +
IaaS = PaaS
[IaaS | PaaS | SaaS ] + [ devops |
open source | noSQL ] = cloud

CLOUDINESS
• An outsourced managed service
• providing hosted computing or functionality
• delivered over the Internet
• offering extreme scalability
• by using dynamically provisioned, multitenant, virtualized
systems, storage, and applications

• controlled via REST APIs
• and billed in a utility manner.

“Cloud? I’ve been doing that since
1988. It’s just the same old thing
with a new name."
- Technohipster

Not new:
virtualization
outsourcing
integration
interwebz

Pretty new:
multitenant
massively scalable
elastic self provisioning
pay as you go
Resulting beneﬁts:
agility
economy of scale
low initial investment
scalable cost/opex
resilience
easy delivery

I recognize that my code will be attacked by talented and
persistent adversaries who threaten our physical,
economic, and national security.

I recognize that my
code will be used in
ways I cannot
anticipate, in ways it
was not designed, and
for longer than it was
ever intended.

I am rugged, not because it is easy, but because it is
necessary... and I am up for the challenge.

RUGGEDIZATION
THEORY

Building solutions to handle
adversity will cause
unintended, positive beneﬁts
that will provide value that
would have been unrealized
otherwise.

RUGGED-ITIES
Maintainability
Availability
Survivability
Defensibility
Security
Longevity
Portability
Reliability

WHAT NEEDS TO HAPPEN
• Focus on real security. FUD doesn’t benefit anyone – figuring
out how to “make it happen” – securely – benefits everyone.

• It’ll
take time for compliance standards to get with the times –
but don’t assume the cloud can’t be compliant – some of your
auditors have actually heard of VMs and know what to do

• Organizations have to accept risk to reap rewards.

• Agile has taught orgs the collaborative approach is best

• Lean has taught orgs to experiment and iterate

source: Gene Kim, “When IT says No @SXSW 2012”

SECURITY SEES...
• They give advice that goes unheeded
• Business decisions made w/o regard of risk
• Irrelevancy in the organization
• Constant bearer of bad news
• Feels ignored by their peers (you know,
those devops guys)
• Inequitable distribution of labor

ANTIPATTERN!

Deploying Software Manually

ANTIPATTERN!

Deploying to a Production-like
Environment Only after Development is
Complete

ANTIPATTERN!
Manual
Conﬁguration
Management of
Production
Environments

CONTINUOUS INTEGRATION

• Check In Regularly

• Create an automated and comprehensive test suite

• Keep build and test short and fast

• All tests must pass before moving on

• Never Go Home on a broken build

• Never comment out failing tests

CONFIGURATION
MANAGEMENT
• Infrastructure as Code (IaC)
• Model driven deployment
• Version control everything
• Know Your Environment if
you want to make it
defensible

RUGGED DEVOPS
BRIDGING SECURITY AND DEVOPS

DEVOPS (+SEC)

• Increasedtrend driven by agile development towards tight
collaboration between developers and operations staff
• Be the “security buddy”
• Embed with projects, don’t be a seagull
• By understanding, be understood
• How secure are things usually when people and teams all
work separately?

THE 6 R’S RUGGED DEVOPS
• repeatable – no manual steps
• reliable - no DoS here
• reviewable – aka audit
• rapid – fast to build, deploy, restore
• resilient – automated reconﬁguration
• reduced - limited attack surface

APPLY RUGGED DEVOPS TO
THE CLOUD
• Start with a Rugged DevOps team
• Use a lot of ﬁrewalls
• Scan your code
• Source to system
• Threat modeling
• Watch for changes
• Pen Testing

PEOPLE AND PROCESS
• Sit near the dev and ops team, better yet, put them
all on the same team
• Track security ﬂaws or bugs in the same bug tracking
system
• Automate whenever possible
• Involve team with vendors
• Measurement over time and clear communication

USE
FIREWALLS...
(A LOT OF
THEM)

Traditional 3-Tier Web Architecture
Firewall

Web Web Web DMZ 1
Firewall

Middle Tier Middle Tier DMZ 2

Firewall

DB LDAP DMZ 3

Cloud Firewalls and DMZ
firewall firewall firewall

Web Web Web DMZ x3

firewall firewall

DMZ x2
Middle Tier Middle Tier

firewall firewall

DB LDAP
DMZ x2

firewall firewall firewall

Web Web Web
Repeatable
firewall firewall
Verifiable
Middle Tier Middle Tier Prod/Dev/Test Matching
firewall firewall Controlled
Automated
DB LDAP

firewall firewall firewall firewall firewall firewall

Web Web Web Web Web Web

firewall firewall firewall firewall

Middle Tier Middle Tier Middle Tier Middle Tier

firewall firewall firewall firewall

DB LDAP DB LDAP

firewall firewall firewall firewall firewall firewall firewall firewall firewall
Web Web Web Web Web Web Web Web Web

Middle Tier Middle Tier Middle Tier Middle Tier Middle Tier Middle Tier

DB LDAP DB LDAP DB LDAP







RUGGED BENEFITS

• Control and trafﬁc whitelisting
• Conﬁg management
• Reproducible, automated and source controlled
• No accidental data traversal across products or
dev/test/prod tiers
• Dev and Test identical to Prod tier

• Scans for OWASP Top Ten and more
• Security Scanning as a Service
• Static and Dynamic scanning
• Integrated into development process
• Dynamic and Static scanning

AUTOMATED PROVISIONING - PIE
• Programmable Infrastructure Environment (PIE)
• Code can be version controlled
• Make Infrastructure as code
• Deﬁned once, deployed many times
• Eliminate repetitive task and human errors
• Rollback capability

• a framework to define, provision, monitor, and control cloud-based
systems
• written in Java, uses SSH as transport, currently supports Amazon
AWS (Linux and Windows) and Microsoft Azure
• takes an XML-based model from source control and creates a full
running system
• to define, provision, monitor, and control cloud-based systems

THREAT MODELING
• Understanding the threat proﬁle of
a system
• Provide a basis for secure design
and implementation
• Discover vulnerabilities
• Provide feedback for the
application security life cycle

p. 29 in Threat Modeling, Swiderski, Snyder

HOST INTRUSION
DETECTION SYSTEM
• Watch the ﬁle system (using hashing and timestamps)
– /etc/
– /usr/bin
–…
• Change control for applications
• Alert on changes and anomalies
• PIE watchdog

PENETRATION TESTING
• Use external and internal penetration
testing
• White box testing vs. Black box testing
• Look for automation opportunities
(ruby, python, …)

BUT WHAT ABOUT SECURITY
TESTING IN MY
SYSTEM?

PUT YOUR CODE THROUGH
THE GAUNTLT

GAUNTLET, N.
AN ATTACK FROM ALL
SIDES

custom attacks dirbuster
metasploit sqlmap

fuzzers nessus

w3af nmap

Your web app You

GAUNTLT
IS BUILT FOR

AN ALWAYS-ATTACKING
ENVIRONMENT FOR
DEVELOPERS

WITH ATTACKS WRITTEN IN
EASY-TO-READ LANGUAGE

ACCESSIBLE TO EVERYONE
INVOLVED IN DEV, OPS,
TESTING, SECURITY, ...

WHY GAUNTLT?

SECURITY DOMAIN
KNOWLEDGE IS
GENERALLY A MYSTERY
TO DEV TEAMS

GAUNTLT ALLOWS DEV
AND OPS AND SECURITY
TO COMMUNICATE AND
COLLABORATE

GAUNTLT JOINS:

THE PHILOSOPHY OF
RUGGED SOFTWARE
&
OUTSIDE-IN
TESTING

LETS LOOK INSIDE A COUPLE
OF THESE FILES

feature for nmap:
nmap.feature
@gauntlet @run

Feature: Run nmap against a target and pass the value of the hostname from the profile.xml.

Background:
Given nmap is installed

Scenario: Verify server is available on standard web ports
Given the hostname in the profile.xml
When I run nmap against the hostname in the profile on ports 80,443
Then the output should contain:
"""
80/tcp open http
443/tcp open https
"""

step definition for nmap:
nmap.rb
Given /^nmap is installed$/ do
steps %{
When I run `which nmap`
Then the output should contain:
"""
nmap
"""
}
end

When /Î run nmap against the hostname in the profile on ports (d+),(d+)$/ do |arg2, arg3|
steps %{
When I run `nmap "#{@hostname}" -p80,443`
}
end

lets run gauntlt with
the nmap.feature
against google.com

running gauntlt with failing tests
wickett$ gauntlt

@gauntlet @run

Background: # features/nmap/nmap.feature:5
Given nmap is installed # features/step_definitions/nmap.rb:2

Scenario:Verify server is available on standard web ports # features/nmap/nmap.feature:8
Given the hostname in the profile.xml # features/step_definitions/profile.rb:1
When I run nmap against the hostname in the profile on ports 8080,443 # features/step_definitions/nmap.rb:12
Then the output should contain: # aruba-0.4.11/lib/aruba/cucumber.rb:98
"""
8080/tcp open http
443/tcp open https
"""
...

Failing Scenarios:
cucumber features/nmap/nmap.feature:8 # Scenario:Verify server is available on standard web ports

1 scenario (1 failed)
4 steps (1 failed, 3 passed)
0m0.341s

running gauntlt with passing tests
wickett$ gauntlt

@gauntlet @run

Background: # features/nmap/nmap.feature:5
Given nmap is installed # features/step_definitions/nmap.rb:2

Scenario:Verify server is available on standard web ports # features/nmap/nmap.feature:8
Given the hostname in the profile.xml # features/step_definitions/profile.rb:1
When I run nmap against the hostname in the profile on ports 80,443 # features/step_definitions/nmap.rb:12
Then the output should contain: # aruba-0.4.11/lib/aruba/cucumber.rb:98
"""
80/tcp open http
443/tcp open https
"""

1 scenario (1 passed)
4 steps (4 passed)
0m1.117s

WALK VS. RUN

• gauntlt has two modes: walk and run

• meaning fast and slow or smoke and full

• This is done by labels in cucumber

• For
each feature you will get to decide if it is a @walk or a
@run test or both

SOME REALIZATIONS

• The core of gauntlt needs to provide a set of
functionality that encourages contributors to write
extensions for their pen testing tools

•A gauntlt DSL (Domain Speciﬁc Language) will arise
with words like target, scan, attack, host...

• Smoke tests and validation vs. long running testing
(nightly/weekly)

JOIN THE PARTY!!
FORK GAUNTLT ON GITHUB

HTTPS://GITHUB.COM/
THEGAUNTLET/GAUNTLT

CLOUD & SECURITY
RESOURCES
• Book: Cloud Security and Privacy (Mather, Kumraswamy, Latif)
• Jericho Forum (collaboration.opengroup.org/jericho/)
• Amazon AWS Security Center (aws.amazon.com/security)
• Austin Cloud User Group (acug.cloudug.org)
• Cloud Security Alliance (cloudsecurityalliance.org)
• CSA Austin Chapter (austincloud.org)
• CSA Security Guidance for Critical Areas in Cloud Computing
• ENISA Cloud Computing Risk Assessment

CONTACT US!

@ERNESTMUELLER

@WICKETT

Rugged DevOps Will help you build ur cloudz

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Rugged DevOps Will help you build ur cloudz

Semelhante a Rugged DevOps Will help you build ur cloudz (20)

Mais de James Wickett

Mais de James Wickett (20)

Último

Último (20)

Rugged DevOps Will help you build ur cloudz