02 - Intro to DevSecOps
02 - Intro to DevSecOps
by TWN
DevSecOps
No part of this publication may be reproduced, copied, transmitted in any
form or by any means, electronic, mechanical, photocopying, recording or
otherwise, without the prior written permission of nnSoftware GmbH
Our mission is enable individual engineers as well as companies to take advantage of the
recent developments in Cloud and DevOps fields, to use technologies and concepts in
order to create efficient, automated, streamlined DevSecOps processes in organisations.
The old way of doing security The new - DevSecOps - way of doing it
Traditional security practices often rely on Delayed security feedback can make it
manual security assessments and more challenging to fix the security issue
reviews, which can be slow and error-prone
The longer it takes to identify and
Manual processes are not well-suited to remediate vulnerabilities, the greater the
the fast-paced, automated nature of potential impact and the higher the
DevOps costs
Microservices
Containers
Cloud platform
Kubernetes
DevSecOps
DevSecOps encourages
automation
collaboration
and a proactive approach to security
helping organizations identify and remediate security issues
earlier in the development lifecycle
what vulnerabilities need to be fixed Bugs are easier to fix the earlier
they are found in the development
lifecycle
Which means less time and costs
Focus: Examining the internal logic, code paths and data flows within
the application.
White Box Testing Advantages: Can provide precise information about the security flaws.
Also helpful for addressing issues related to code quality and design
flaws.
Knowledge: No access to the source code and relies solely on the system's
inputs and outputs.
Black Box Testing Advantages: Simulates real-world attacks and provides a more user-centric
perspective on security. Testers do not need to be familiar with the application's
codebase.
Limitations: May not uncover all security vulnerabilities that can be identified
through code-level inspection, and it may miss some complex or logic-based
vulnerabilities.
There is always a chance that security issues slip into production environment
Or that 3rd-party vulnerabilities appear after production deployment
That’s why we need proper continuous logging, monitoring and alerting in place, that:
More efficient
Security Engineer focuses on securing Broader approach by integrating security into entire
systems, networks and infrastructure DevOps process
Bridging the gap between Dev, Ops and Security
teams
Help automate security checks
Help Devs and Security Engineers to discover, visualize
and fix efficiently
It’s a way of working together Many roles working together to integrate security
It ‘s about shared responsibility and shifting Divide and share responsibilities
security left No dedicated DevSecOps engineer that orchestrates
Catch security issues early and develop everything, teams should pro-actively collaborate
more secure applications
Everybody is busy with their daily tasks and Often someone is needed in the company
responsibilities that actually make things happen
Engineers don’t have time to think about DevSecOps Someone whose main focus and task is to
Concepts are not yet ingrained into every single set up processes and making sure teams
engineer, so that they pro-actively build DevSecOps work together, share knowledge and
processes responsibility
Copyright 2023 nnSoftware GmbH. All rights reserved.
Varies between organizations
Specific roles and responsibilities associated with implementing
DevSecOps vary between organizations