DevSecCon London 2017: The flaws in hordes, the security in crowds by Mike Shema

•

0 likes•308 views

DevSecCon

– Clint Eastwood, The Good, the Bad, and the Ugly.
“You see, in this world there’s
two kinds of people, my friend:
Those with loaded guns and
those who dig. You dig.”

– Eli Wallach, The Good, the Bad, and the Ugly.
“There are two kinds of spurs,
my friend. Those that come in
by the door; those that come in
by the window.”

Uneasy Alliances
“What’s the price for this vuln?” 
— Bounties
“What’s the cost to fix this vuln?” 
— DevOps
“What’s the value of finding vulns?” 
— CSOs

Some Observations of Swarms of Strange
Insects, and the Mischiefs done by them.

Bounties are an imperfect proxy for risk,
where price implies impact.
$0 — $15K
~$800 avg.
$50
XSS self,
no auth
$10,000
XSS any auth’d user, 
access sensitive info

Bounties are an imperfect proxy for work,
where earnings often diverge from effort.

Noise increases
cost of discovery
and reduces
efﬁciency.

Volume— 
Reports/day 
Percent valid
Triage—
Time/report 
People/report + 
[Baseline]

-cost 
+time
-cost 
-time
+cost 
+time
+cost 
-time

Scanners
Overlaps, gaps, and
ceilings in capabilities.
Fixed-cost, typically
efficient, but still require
triage and maintenance.

Days Since Valid (Any) Report
2016 7 (4) 16 (8) 33 (14)
2015 4 (1) 10 (5) 23 (11)
50% 80% 95%
Days since any report:
2, 5, 11

– Mike’s Axiom of AppSec
“We’ll always have bugs. 
Eyes are shallow.”

BugOps vs. DevOps
Chasing bugs isn’t a strategy.

As we move to
security as code,
code moves to
inevitable legacy.

Threat Modeling
DevOps exercise guided by security.
Influences design.
Informs implementation.
Increases security awareness.

“You’re not using HTTPS.”
“Use HTTPS.”
“Seriously. Please use HTTPS.”
Let’s Encrypt.

Bounty ranges as a proxy for SDL, 
where price implies maturity.
$ 1 Experimenting
$ 1,000 Enumerating
$ 10,000 Exterminating
$ 100,000 Extinct-ifying

Security from Inventory
Enumerate your apps.
Generate their
dependency graphs.
Identify ownership.

Security from Crowds
Provide reasonable
threat models.
Report via issue
trackers.
Automate
reproduction steps.

Measure vuln discovery effort
Monitor risk for trends
Illuminate brittle design
Security from DevSecOps

Join the conversation #DevSecCon
Thank You!

Join the conversation #DevSecCon
Questions?
@CodexWebSecurum

R — 
www.r-project.org
RStudio — 
www.rstudio.com
data.table
ggplot

A cacophony of hordes.
A scrutiny of crowds.

Although the Security Profession has always aspired to prevent adverse events, we have found ourselves stymied in the world of Reactive Detection—the path most commonly taken in one’s pursuit of ISO compliance. Our webinar will explore the new emerging paradigm Artificial Intelligence (AI) and what it portends for the future. Main points covered: • Security Profession always aspired to be Proactive, but found ourselves stymied in the World of the Reactive. • Traditional boundaries of interest are growing ever more porous, exacerbated by the exponential growth of the IoT. • With the advance of AI we now have a choice: remain ensconced in the paradigms of the past or evolve to the new proactive paradigm which AI portends. Presenter: John McClurg serves as Vice President and Ambassador-At-Large of Cylance, where he is responsible for building Security and Trust programs & operational excellence efforts. Prior to Cylance, he served as the CSO of Dell, Honeywell, and Lucent and in the U.S. Intelligence Community, as a twice-decorated member of the Federal Bureau of Investigation (FBI). He also served as a Deputy Branch Chief of CIA where he helped to establish the new Counterespionage Group and was responsible for the management of complex counterespionage investigations. McClurg was voted one of America’s 25 most influential security professionals. Link of the recorded session published on YouTube: https://youtu.be/D76BXU15fCY

R af dWilliam L. McGill

Risk Analysis for Dummies

William L. McGill

Got Myth? Myths in Software Engineering

Thomas Zimmermann

How Credential Stuffing is Evolving - PasswordsCon 2019

Jarrod Overson

Mitun Zavery Senior Engineer at Sonatype Bad actors have recognized the power of open source and are now beginning to create their own attack opportunities. This new form of assault, where OSS project credentials are compromised and malicious code is intentionally injected into open source libraries, allows hackers to poison the well. In this session, Mitun will explain how both security and developers must work together to stop this trend. Or, risk losing the entire open source ecosystem. Analyze, and detail, the events leading to today’s “all-out” attack on the OSS industry Define what the future of open source looks like in today’s new normal Outline how developers can step into the role of security, to protect themselves, and the millions of people depending on them

Trusted, Transparent and Fair AI using Open Source

Animesh Singh

Web security – everything we know is wrong cloud version

Eoin Keary

Black ops 2012Dan Kaminsky

Zen and the art of Security Testing

TEST Huddle

Some security experts would tell you that security testing is very different from functional or non-functional software testing. They are wrong. Having worked on both sides, Paco gives 3 specific recommendations for how testers can make significant contributions to the security of their software and applications by making small changes to the way they do their software testing. The first technique has to do with selecting points in the user journey that are ripe for security testing. The second is to leverage some common free tools that enable security tests. The final technique is adjusting old school boundary value testing and equivalence class partitioning to incorporate security tests. The result is a lot of security testing done and issues fixed long before any security specialists arrive. Key Takeaways: -Great places in the user journey to inject security tests - Ways to augment existing test approaches to cover security concerns - Typical security tools that are free, cheap, and easy for software testers

Allianz Global CISO october-2015-draft

Eoin Keary

Measuring Micro-services. Richard Rodger

Future Insights

FOWA London 2015 Micro-service systems deliver wonderful adaptability to business needs, easy scalability, and low-risk deployment. What's not to like? You also end up with a system that's hard to understand, measure and predict. Traditional approaches to monitoring simply aren't powerful enough to handle the emergent properties of a system with lots of moving parts. The solution is to apply the scientific method! Anything can be measured. Uncertainty can be reduced, and stability can be an emergent property. We just have to learn the lessons that the natural world can teach us.

Practical Malware Analysis The Hands-On Guide to Dissecting Malicious Softwar...

lephuocthinh2

Measuring Micro-services - Richard Rodger - Codemotion Rome 2015

Codemotion

Codemotion Rome 2015 - Micro-service systems deliver wonderful adaptability to business needs, easy scalability, and low-risk deployment. What's not to like? You also end up with a system that's hard to understand, measure and predict. Traditional approaches to monitoring simply aren't powerful enough to handle the emergent properties of a system with lots of moving parts. The solution is to apply the scientific method! Anything can be measured. Uncertainty can be reduced, and stability can be an emergent property. We just have to learn the lessons that the natural world can teach us.

Richardrodger microxchgio-feb-2015-final

Richard Rodger

The micro-service architecture has changed the game for software development. It provides the first scalable, effective component model for software systems. By embracing the organic, dynamic and chaotic nature of micro-services, you can built fault-tolerant, scalable and reactive systms. But there is a dark side. Things can get out of control very quickly. As the number of micro-services, and messages and interactions between them grow, how do you keep control? How do you retain understanding of the system? How can you offer any commitments about its behaviour to your CEO? The answer is to embrace the complexity of the system, and recognize that it has emergent properties. Rather than auditing and tracking technical behaviour, measure the behaviour you care about, the business outcomes. This allows you to understand the effects of new deployments and failures at the right level.

Online Gaming Cyber security and Threat Model

Eoin Keary

We cant hack ourselves secure

Eoin Keary

Dan Guido SOURCE Boston 2011

Source Conference

Web security-–-everything-we-know-is-wrong-eoin-kearydrewz lin

Thane Barnier MACE 2016 presentation

Jeff Zahn

Frustrated with Vulnerability Assessments you must put your Blood, Sweat, and...

Ivanti

Continuous vulnerability assessment and remediation should be part of every organization’s security practices. If only the time and manual work involved in that period between identifying a vulnerability and deploying a software update wasn’t such a drain on IT teams. Each time Security hands off a vulnerability report, it can take IT hours of research to identify how to resolve it. And that’s time an attacker can use to gain a foothold in the organization and access to sensitive data. Want a better way? Join us to learn how Ivanti and BeyondTrust drive down time, cost, and consequences by integrating vulnerability scanning and patch management and automating their holistic solution.

Making the case for sandbox v1.1 (SD Conference 2007)

Dinis Cruz

Opsec for security researchers

vicenteDiaz_KL

DevSecCon London 2019: Workshop: Cloud Agnostic Security Testing with Scout S...

DevSecCon

Xavier Garceau-Aranda Senior Security Consultant at NCC Group With the steady rise of cloud adoption, a number of organizations find themselves splitting their resources between multiple cloud providers. While the readiness to deal with security in cloud native environments has been improving, the multi-cloud paradigm poses new challenges. The workshop will aim to familiarize attendees with Scout Suite (https://github.com/nccgroup/ScoutSuite), a key component of NCC Group’s cloud agnostic approach to security assurance. Scout Suite is an open source multi-cloud security-auditing tool, which enables security posture assessment of cloud environments. Using the APIs exposed by cloud providers, Scout Suite gathers configuration data for manual inspection and highlights risk areas. Rather than pouring through dozens of pages on the web consoles, Scout Suite provides a clear view of the attack surface automatically. The following cloud providers are currently supported: - Amazon Web Services - Microsoft Azure - Google Cloud Platform - Oracle Cloud Infrastructure - Alibaba Cloud During the workshop, attendees will leverage Scout Suite to assess a number of cloud environments designed to simulate typical flaws. We will display how the tool can be leveraged to quickly identify and help with remediation of security misconfigurations.

DevSecCon London 2019: How to Secure OpenShift Environments and What Happens ...

DevSecCon

Jan Harrie Security Analyst at ERNW GmbH OpenShift by Red Hat is one of the major Platform as a Service (PaaS) solutions on the market. It is used to automatically deploy Kubernetes clusters and provides useful extensions for cluster management mixed with some magic under the hood. Instantiating a Kubernetes cluster is often a crucial step in setting up a modern application stack. But be aware – a lot of configuration parameters are awaiting you. And here several misconfigurations may occur that can lead up to a compromise of the cluster. Privileged containers, tainting of masters and executing workloads on them, missing role-based access controls, and misconfigured Service Accounts are part of the problem. In this talk, I will explain which configuration parameters of an OpenShift environment are critical to ensure the overall security of the deployed Kubernetes clusters. Implications of misconfigurations will be demonstrated during live demos. Finally, recommendations for a secure configuration are provided.

Similar to DevSecCon London 2017: The flaws in hordes, the security in crowds by Mike Shema

Fix What Matters

Ed Bellis

Healthcare forum perry-david m-everything you know is wrong!

ISSA LA

DevSecCon London 2019: Are Open Source Developers Security’s New Front Line?

DevSecCon

Trusted, Transparent and Fair AI using Open Source

Animesh Singh

Web security – everything we know is wrong cloud version

Eoin Keary

Black ops 2012Dan Kaminsky

Zen and the art of Security Testing

TEST Huddle

Allianz Global CISO october-2015-draft

Eoin Keary

Measuring Micro-services. Richard Rodger

Future Insights

Practical Malware Analysis The Hands-On Guide to Dissecting Malicious Softwar...

lephuocthinh2

Measuring Micro-services - Richard Rodger - Codemotion Rome 2015

Codemotion

Richardrodger microxchgio-feb-2015-final

Richard Rodger

Online Gaming Cyber security and Threat Model

Eoin Keary

We cant hack ourselves secure

Eoin Keary

Dan Guido SOURCE Boston 2011

Source Conference

Web security-–-everything-we-know-is-wrong-eoin-kearydrewz lin

Thane Barnier MACE 2016 presentation

Jeff Zahn

Frustrated with Vulnerability Assessments you must put your Blood, Sweat, and...

Ivanti

Making the case for sandbox v1.1 (SD Conference 2007)

Dinis Cruz

Opsec for security researchers

vicenteDiaz_KL

Similar to DevSecCon London 2017: The flaws in hordes, the security in crowds by Mike Shema (20)

Fix What Matters

Healthcare forum perry-david m-everything you know is wrong!

DevSecCon London 2019: Are Open Source Developers Security’s New Front Line?

Trusted, Transparent and Fair AI using Open Source

Web security – everything we know is wrong cloud version

Black ops 2012

Zen and the art of Security Testing

Allianz Global CISO october-2015-draft

Measuring Micro-services. Richard Rodger

Practical Malware Analysis The Hands-On Guide to Dissecting Malicious Softwar...

Measuring Micro-services - Richard Rodger - Codemotion Rome 2015

Richardrodger microxchgio-feb-2015-final

Online Gaming Cyber security and Threat Model

We cant hack ourselves secure

Dan Guido SOURCE Boston 2011

Web security-–-everything-we-know-is-wrong-eoin-keary

Thane Barnier MACE 2016 presentation

Frustrated with Vulnerability Assessments you must put your Blood, Sweat, and...

Making the case for sandbox v1.1 (SD Conference 2007)

Opsec for security researchers

More from DevSecCon

DevSecCon London 2019: Workshop: Cloud Agnostic Security Testing with Scout S...

DevSecCon

DevSecCon London 2019: How to Secure OpenShift Environments and What Happens ...

DevSecCon

DevSecCon London 2019: A Kernel of Truth: Intrusion Detection and Attestation...

DevSecCon

Matt Carroll Infrastructure Security Engineer at Yelp "Attestation is hard" is something you might hear from security researchers tracking nation states and APTs, but it's actually pretty true for most network-connected systems! Modern deployment methodologies mean that disparate teams create workloads for shared worker-hosts (ranging from Jenkins to Kubernetes and all the other orchestrators and CI tools in-between), meaning that at any given moment your hosts could be running any one of a number of services, connecting to who-knows-what on the internet. So when your network-based intrusion detection system (IDS) opaquely declares that one of these machines has made an "anomalous" network connection, how do you even determine if it's business as usual? Sure you can log on to the host to try and figure it out, but (in case you hadn't noticed) computers are pretty fast these days, and once the connection is closed it might as well not have happened... Assuming it wasn't actually a reverse shell... At Yelp we turned to the Linux kernel to tell us whodunit! Utilizing the Linux kernel's eBPF subsystem - an in-kernel VM with syscall hooking capabilities - we're able to aggregate metadata about the calling process tree for any internet-bound TCP connection by filtering IPs and ports in-kernel and enriching with process tree information in userland. The result is "pidtree-bcc": a supplementary IDS. Now whenever there's an alert for a suspicious connection, we just search for it in our SIEM (spoiler alert: it's nearly always an engineer doing something "innovative")! And the cherry on top? It's stupid fast with negligible overhead, creating a much higher signal-to-noise ratio than the kernels firehose-like audit subsystems. This talk will look at how you can tune the signal-to-noise ratio of your IDS by making it reflect your business logic and common usage patterns, get more work done by reducing MTTR for false positives, use eBPF and the kernel to do all the hard work for you, accidentally load test your new IDS by not filtering all RFC-1918 addresses, and abuse Docker to get to production ASAP! As well as looking at some of the technologies that the kernel puts at your disposal, this talk will also tell pidtree-bcc's road from hackathon project to production system and how focus on demonstrating business value early on allowed the organization to give us buy-in to build and deploy a brand new project from scratch.

DevSecCon Seattle 2019: Containerizing IT Security Knowledge

DevSecCon

Kristóf Tóth Software Engineer at Avatao The world is getting eaten alive by software. At this point, almost nothing can be done without interacting with some sort of software system. Not even buying your groceries. As we keep dumping out huge piles of code like there is no tomorrow, our far from perfect systems keep getting worse and worse from a security standpoint. What could possibly go wrong? We believe that education is the missing link. As appsec is still a curiosity topic on top universities, freshly graduated engineers simply have no clue. And how could they? The number of programmers keeps on doubling every few years and generations of software professionals are stuck without a proper background in ITSec. As this trend continues, our responsibility to do something about this is on the rise. In hopes of fighting this trend, we, at Avatao, have decided to share some of our dreams with the community. Our Tutorial Framework allows you to easily create interactive learning environments running inside Docker containers. These environments are capable of automatically guiding users through a set of topics by allowing them to interact with real software through a simple web browser. Users can attack webservices, write code to fix them or use a terminal to deploy websites by creating and pushing git tags. Nothing here is a mock-up: Every software component is real. In this talk, I am going to demonstrate the capabilities of the framework, talk about the technology behind it and explore some use cases for it. During the session we will open source the framework with the hope of creating a better, secure future together.

DevSecCon Seattle 2019: Decentralized Authorization - Implementing Fine Grain...

DevSecCon

Sitaraman Lakshminarayanan Sr Security Architect at Pure Storage Authorization has two components – Policy Definition and Policy Enforcement. Traditionally both used to be centralized and we spent all the time Integrating products- Built or Bought with Centralized Access Management. This typically led to increased cycle time to change any access policy or change software/deployment to fit into one particular authorization model. When that doesn’t fit, we would end up with multiple authorization enforcements written in different languages with or without any adherence to any standards such as XACML or others. Imagine building few different or hundreds of products or services or micro services and you have to centrally manage all possible access policies. It’s definitely not a scalable solution in fast moving CI/CD world. Now imagine a way where every developers or products can externalize its authorization and we can modify authorization enforcement in a consistent manner? Imagine where developers can write their own implementation of how authorization should be enforced for their environment? Remember there is no one size fits all authorization policy. A policy that works for your environment does not work for my environment – for any number of reasons from Risk management to type of business applications. Open Policy Agent provides a consistent way to write authorization logic and expose it as REST API. Applications can easily integrate with OPA and can also write their own authroziation logics. Whether you are shipping products to customers or integrating a Product or Service into your environment, how awesome it would be to enforce your own authorization rules instead of changing your business process of who can gain access to what features. In this talk we will explore the benefits of Decentralized Authorization and how to use Open Policy Agent to achieve decentralized authorization. A closer look at few applications /integrations whether it is REST API /Micro Services, or Kubernetes to control various authorization policies as to who can deploy/what can you deploy. We will also look at how to build Integration tests to check our authorization policies.

DevSecCon Seattle 2019: Liquid Software as the real solution for the Sec in D...

DevSecCon

DevSecCon Seattle 2019: Fully Automated production deployments with HIPAA/HIT...

DevSecCon

Matt Lavin Software Architect at LifeOmic It's possible to have rapid feature delivery and happy developers without sacrificing high security and compliance. At LifeOmic, we've built an automated change management system that allows production deployments without slow human approval. We maintain HIPAA and HITRUST compliance while still allowing continuous delivery. I'll show how to collect data from BitBucket, Jenkins, and security scan tools to ensure that the approved processes have been followed. You'll hear how fast production approval incentivizes developers to follow good practices, and become advocates for following the process instead of pushing against it. Automating process checks as a gate to deployments is a great framework for promoting the behavior you want in your organization. Don't give up on rapid feature delivery just because you work in a regulated industry.

DevSecCon Singapore 2019: Four years of reflection: How (not) to secure Web A...

DevSecCon

Julian Berton Preventing a company from becoming the newest data breach statistic can be a daunting prospect. Especially working within a company that employs hundreds of engineers pushing code to production daily, it often feels like everything is on fire and the holy grail of producing a security inspired product is but a dim light growing further and further away. The same feeling is true for security aware engineers being pushed to develop products quickly but also expected to consider quality assurance, operations, security and the reliability of their application or service. To help reduce the bleeding and build more security aware applications at scale, a balance of firefighting, preventative initiatives, automation and "JIT" education is required. So strap yourself in while we take you on a journey through 4 years of security successes and epic failures: * Automation - Implementing a secure-by-default build system (Buildkite) that makes detecting vulnerable dependencies (Snyk), storing secrets (AWS Secrets Manager) and scanning Docker containers, an effortless process. * Prevention - Eradicate several classes of bugs by selecting secure architectural patterns and using automated scripts to detect operational misconfigurations like dangling DNS entries, open S3 buckets, secrets checked into source code and repositories that have been made accidentally public. * "JIT” Education - Changing a companies security culture with RFC's for security standards, security integrated PIR via bug bounty program reports, visibility through security maturity frameworks (BSIMM).

DevSecCon Singapore 2019: crypto jacking: An evolving threat for cloud contai...

DevSecCon

Rahul Kumar & Rupali Dash In the current era of blockchain technology, mining crypto currency is one of the biggest hit. The talk covers how the attackers use the insecure containers to mine crypto currency and earn million dollar profits. Cryptojacking activity surged to its peak in December 2017, when more than 8 million cryptojacking events were blocked by many intrusion detection companies. While there have seen a slight fall in activity in 2018, it is still at an elevated level, with total cryptojacking events blocked in July 2018 totalling just less than 5 million. The talk will cover how the mining activities has been done using browsers as well as cloud containers. We will also discuss how the cloud provides like amazon, azure and go are detecting such kind of activities and how minor misconfigurations leads to million dollar currency mining. The talk will also cover how 3rd party security providers like symantec and z-scalar and other intrusion detection system has configured signatures to block such kind of attacks. As well as from a sec-ops prospective what configuration checks should be done to prevent against such kind of attacks as well as detection of attacks. It will also cover some case studies and attack scenarios of mining Monero and the huge financial losses because of this attacks.

DevSecCon Singapore 2019: Can "dev", "sec" and "ops" really coexist in the wi...

DevSecCon

Trinh Tran & Dennis Stötzel Are you trying to stay secure while developing and running a bunch of services and applications every day? So are we and it’s a huge pain in the… pipeline. We have been juggling these aspects while working with one of the biggest insurance companies in the world. In this talk, we will share our experiences of the last three years: Trinh, as a software engineer in Vietnam and Dennis, as a security engineer in Germany. We will present our experiences of making "dev", "sec" and "ops" coexist – without sparing any dirty details. Our goal has always been fast delivery and secure applications using pipelines, containers, orchestration, and the cloud. Let us explain which of these goals we have met and which remain goals, where we messed up and where we found glory. We will cover the following topics in our talk: * Evolution of our project, from beginning with four engineers running in one office, to expanding to fifty engineers coming from three continents and different backgrounds, * Development, delivery and security as a requirement in an agile project, * The good, the bad and the ugly in technology, architecture and infrastructure.

DevSecCon Singapore 2019: Workshop - Burp extension writing workshop

DevSecCon

Sanoop Thomas & Samandeep Singh Burp suite is the de-facto proxy application for web security testers. This hands-on workshop will explore the different capabilities of burp proxy application, also dive into the extensions and tooling options to perform improved application security test cases. The workshop will start with a quick overview of burp usage, different settings, features, some commonly useful extensions and then explore deep into its extension APIs to build your own custom extensions. We will provide a suitable development environment in Java and Python platforms. This will be a hands-on workshop and participants will learn how to automate different application security test scenarios and build burp extensions with the help of templates.

DevSecCon Singapore 2019: Embracing Security - A changing DevOps landscape

DevSecCon

Cameron Townshend Today’s pace of innovation and need to out “innovate” competitors can often cause developers to bypass key portions of Gene Kim’s Three Ways of DevOps - specifically to never pass a known defect downstream and emphasize performance of the entire system. As we embrace movements like CI, CD and Devops to cut down on release cycles - and innovate faster, we as developers must also embrace the reality that the risk landscape is too complex to leave “security” to just those with security in their title. Traditional methods do not cut it anymore – it’s time for DevSecOps. Instinctively, we understand how critical this is. In Sonatype’s recent 2018 DevSecOps Community report, where 2,076 IT professionals were surveyed, 48% of respondents admitted that developers know application security is important, but they don’t have the time to spend on it. Done properly, DevSecOps practices shouldn’t interrupt the DevOps pipeline - but instead aid it - preventing costly rebuilds and build breaks, down the road. By creating automated governance and compliance guardrails that are embedded early and throughout the software development lifecycle, developers have transparent access to digital guardrails integrated within our native tools — an approach that ensures security is being built in without slowing us down. These instant feedback loops detailing good or bad components have been shown to increase developer productivity by as much as 48%. Over time, this approach ensures developers procure the best components from the best suppliers, while continuously tracking components across the entire lifecycle. Attendees of this session will walk away with: Real-world examples of how large and small companies are implementing DevSecOps practices in their own delivery pipelines, and increasing developer awareness to risks Key insights from 2,076 of their peers who participated in the 2018 DevSecOps community report - including where most mature DevOps practices are focusing their security efforts A walkthrough of how security principles have been embedded in a CICD pipeline and what standards for implementation are beginning to follow suite

DevSecCon Singapore 2019: Web Services aren’t as secure as we think

DevSecCon

Tilak T Web-Services are taking over the world. Rest-framework is accelerating this development, because of its ease and flexibility. Developers often use and develop REST-based applications because it's exciting to work with. But they forget about security which leads to compromised and exploited applications. For instance, in more recent security tests against Web Services that my team executed, we found that vulnerabilities like Insecure Deserialization, XML External Entities, Server-Side Template Injection and Authorization Flaws are quite prevalent. I have found some simple steps that engineering teams can take towards finding and fixing such vulnerabilities with Web Services. This talk is offering a holistic perspective on finding and fixing some uncommon flaws that will be replete with anecdotes and examples of secure and insecure code. I will also delve into automating SAST and DAST tools using Robot-Framework to identify such flaws in Web-Services.

DevSecCon Singapore 2019: An attacker's view of Serverless and GraphQL apps S...

DevSecCon

Sharath Kumar Ramadas Serverless Technology (Functions as a Service) is fast becoming the next "big thing" in the world of distributed applications. Organizations are investing a great deal of resources in this technology as a force-multiplier, cost-saver and ops-simplification cure-all. Especially with widespread support from cloud vendors, this technology is going to only become more influential. However, like everything else, Serverless apps are subject to a wide variety of attack possibilities, ranging from attacks against access control tech like JWTs, to NoSQL Injection, to exploits against the apps themselves (deserialization, etc) escalating privileges to other cloud components. On the other hand GraphQL (API Query Language) is the natural companion to serverless apps, where traditional REST APIs are replaced with GraphQL to provide greater flexibility, greater query parameterization and speed. GraphQL is slowly negating the need for REST APIs from being developed. Combined with Serverless tech/Reactive Front-end frameworks, GraphQL is very powerful for distributed apps. However, GraphQL can be abused with a variety of attacks including but not limited to Injection Attacks, Nested Resource Exhaustion attacks, Authorization Flaws among others. This talk presents a red-team perspective of the various ways in which testers can discover and exploit serverless and/or GraphQL driven applications to compromise sensitive information, and gain a deeper foothold into database services, IAM services and other other cloud components. The talk will have some demos that will demonstrate practical attacks and attack possibilities against Serverless and GraphQL applications. The author will release an intentionally vulnerable Serverless and GraphQL app at the end of the talk for the benefit of the audience and the security community at large.

DevSecCon Singapore 2019: The journey of digital transformation through DevSe...

DevSecCon

Nadira Bajrei IT Continuous Improvement and Knowledge Management at Bank Mandiri Tbk We all know that the Banking industry is highly regulated. But due to recent changing factors, we had to trigger something we call transformation. Two of the most important reasons why we need transformation are firstly digital disruption, a wave our industry is hard pushed to follow, and secondly the evolving customer expectation and competitive environment, which are impacting the way organisations are delivering value. We need a new way of working to help us stay relevant in the market. This session will focus on our journey as one of the biggest banks in Indonesia to do digital transformation into DevOps while maintaining security compliance requirements. I will elaborate on the main reason why we need transformation, our journey roadmap, the step by step adoption of CALMS Values in our organisation and how we faced challenges from internal and external site.

DevSecCon Singapore 2019: Preventative Security for Kubernetes

DevSecCon

Liz Rice The latest Kubernetes version provides many security-related enhancements and controls, but it is far from being secure by default. Kubernetes is a complex orchestration platform with many different implementations, across multi-cloud/hybrid environments. Configuring it to comply with security best practices and specific security requires time and expertise that most organizations don’t possess. Aqua’s open source tools arm Kubernetes administrators and developers with an easy way to identify weaknesses in their deployments so that they can address those issues before they are exploited by attackers. During this presentation, we’ll review how these open source tools offer preventive security for Kubernetes: Kube-Bench: checks a Kubernetes cluster against 100+ checks documented in the CIS Kubernetes Benchmark. Kube-Hunter: conducts penetration tests against Kubernetes clusters that hunt for exploitable vulnerabilities and misconfiguration - both from outside the cluster as well as inside it (running as a pod)

DevSecCon London 2018: Is your supply chain your achille's heel

DevSecCon

COLIN DOMONEY The advent of DevOps and large scale automation of software construction and delivery has elevated the software supply chain – and its underpinning delivery pipeline – to mission critical status in any modern enterprise. The increased velocity of modern pipelines and the removal of manual checks and balances has meant that modern pipelines are potential single points of failure in the delivery of secure software. Automotive and consumer electronics industries have long understood the need for both provenance (understanding the origin of materials) and veracity (ensuring the integrity of their manufacturing processes) in their supply chains; this presentation will address threats to software supply chains and practical approaches to reducing the fragility of your supply chain. Several examples of software supply chain failures will be presented and deconstructed to understand the typical failure modes. At the most elementary level many pipelines are poorly constructed with low levels of repeatability and poor test coverage, in other organisations there is a lack of governance over the supply chain allowing careless or willingly negligent actors to subvert or bypass controls or testing within the pipeline. There is also no standard mechanism to ensure a ‘chain of custody’ within a pipeline due to a lack common interchange format between tools, or a standard manner to represent the steps within a pipeline build process. This presentation will cover approaches (using ‘people and process’) in enforcing governance within a supply chain by describing best practices used in large-scale AppSec programmes. Several emerging technology initiatives will be presented: Google’s Grafeas is a means to ensure vulnerability information is represented in a uniform manner across all steps of a pipeline process, while In-Toto is a project to formally enforce the integrity of a pipeline process. A reference secure pipeline will be presented demonstrating both tools working in symphony, along with standard open source and commercial AppSec tools. Finally the pipeline itself may become the Achille’s Heel in an organisation – many pipelines are not sufficiently hardened and are themselves open to attack by use of vulnerable components and their extensible nature, often along with very wide open permissions. Guidance will be given on hardening of typical pipelines, and a fully secured ephemeral Jenkins pipeline will be demonstrated. Benefits of this Session: The attendee will gain an increased awareness of the pivotal importance of the software supply chain, and gain an understanding of some common failure modes and weaknesses. Most importantly the attendee will come away with practical guidance on enforcing higher levels of governance on their supply chain without reducing delivery velocity, as well as how to harden the pipeline infrastructure itself.

DevSecCon London 2018: Get rid of these TLS certificates

DevSecCon

Paweł Krawczyk Most network services and daemons now offer TLS transport protection and their managing certificates and TLS configuration for server farms may use more resources than actual configuration of these services. What if you could get rid of all this complexity and replace it by single transport protection protocol, securing all of the traffic between your servers trasparently and with single centralized key and configuration management? This will be a story of a successful implementation of IPSec protocols, largely and undeservedly forgotten in that purpose, for securing a farm of production cloud servers, with configuration centrally managed with Ansible.

DevSecCon London 2018: Open DevSecOps

DevSecCon

PETKO D. PETKOV Thanks to the DevSecOps philosophy a growing number of organisations around the world are ensuring their businesses are set up with the security in mind from the get-go. DevSecOps is taking the world by storm. This talk is about how to introduce DevSecOps in your organisation with ready-made, zero-cost, open source templates accessible to everyone. The talk will introduce the OpenDevSecOps project and show many practical examples of how to easily deploy security testing infrastructure on top of existing and well-established development tools.

DevSecCon London 2018: Building effective DevSecOps teams through role-playin...

DevSecCon

MIKE SHEMA Effective appsec emerges from DevSecOps tactics like feedback loops, automation, and the flexibility to respond to situations quickly. These tactics emphasize process and tools, sometimes neglecting the knowledge and skills of working with others to build and maintain apps. And the solutions they strive for don’t always catch the importance of how different users can have different threat models. On the technology side of appsec we have clouds, top 10 lists, and tools. But we haven’t built up equivalent resources, references, or models for the people we build apps with and who we build them for. This presentation dives into specific techniques and references for working with people and building threat models that go beyond basic technical concerns. Tabletop role-playing games are a great model for understanding and building skills that are important to DevSecOps teams. They encourage communication, collaboration, and the achievement of shared goals. And they also face the same challenges in solving conflicts, avoiding derailing behaviors, and ensuring everyone participates. Come discover how RPGs can positively influence your security teams. Security is an integral part of DevSecOps. And, yes, it’s made of people.

More from DevSecCon (20)