[AZ-400] DevSecOps And Tools

This blog talks about DevSecOps and how its all about introducing security earlier in the life cycle of application development, thus minimizing vulnerabilities and bringing security closer to IT and business objectives.

The technologies that are covered in this blog are a part of the Azure DevOps environment. If it’s something in which you have an interest or you want to learn, then you can visit our previous blog to know more about the [AZ-400] Microsoft Azure DevOps certification.

In this blog we will be covering:

1. Why DevSecOps Is Important?
2. DevOps Vs. DevSecOps: The Integration
3. How To Integrate The DevSecOps?
4. Categories Of DevSecOps

Why DevSecOps Is Important?

IT infrastructure has undergone huge changes in recent years. The shift to dynamic provisioning, shared resources, and cloud computing has driven benefits around IT speed, agility, and cost, and all of this has helped to improve application development.

DevOps Vs. DevSecOps: The Integration

Integrating security into DevOps to deliver DevSecOps requires new mindsets, processes, and tools. Security and risk management leaders need to adhere to the collaborative, agile nature of DevOps to be seamless and transparent in the development process, making security as silent and seamless as possible. However, this is difficult for two different disciplines.

How To Integrate The DevSecOps?

1. A developer creates code within a version control management system.
2. The changes are committed to the version control management system.
3. Another developer retrieves the code from the version control management system and carries out an analysis of the static code to identify any security defects or bugs in code quality.
4. An environment is then created, using an infrastructure-as-code tool, such as Chef. The application is deployed and security configurations are applied to the system.
5. A test automation suite is then executed against the newly deployed application, including back-end, UI, integration, security tests, and API.
6. If the application passes these tests, it is deployed to a production environment.
7. This new production environment is monitored continuously to identify any active security threats to the system.

Categories Of DevSecOps 

Code Security Tools

1. SonarQube / SonarCloud
2. Source Guard
3. Shiftleft Scan
4. checkmarx
5. Veracode Greenlight

Build Security Tools

1. Burp Suite
2. Zed Attack Proxy (ZAP)
3. ModSecurity
4. WhiteSource Bolt
5. Skipfish
6. Veracode SourceClear

Code Security Tools

1. Yelp
2. CredScan
3. Changeme
4. Secret-code-scanner
5. Veracode Greenlight

Artifactory Security Tools

1. Jfrog Xray
2. Kroll Parser
3. Archiva
4. Aqua
5. Anchore

SCA Security Tools

1. Qualys
2. Snyk
3. WhiteSource
4. Veracode
5. CheckMarx

Container Security Tools

1. Aqua Security Tools
2. Anchore Container security
3. Whitesource
4. Twistlock
5. Qualis
6. Clair

Penetration Testing Tools

1. Qualys
2. Snyk
3. WhiteSource
4. Veracode

Threat Modelling Tools

1. OWASP Threat Dragon
2. Microsoft Threat Modelling Tool 2016.
3. Threat Modeler
4. Raindance
5. Threatspec
6. PyTM

Website Vulnerability Tools

1. URL Freezer
2. SQLi Scanner
3. XSS Scanner
4. Drupal
5. Joomla

Related/References

• [AZ-400] Microsoft Azure DevOps Certification Exam: Everything You Need To Know
• [AZ-400] Azure DevOps Certification Path
• [AZ-400] Azure DevOps Services for Beginners
• [AZ-400] Designing and Implementing Microsoft DevOps Solutions [Official Page]
• SonarCloud Azure DevOps | Integrating SonarCloud In Azure
• Veracode – SourceClear SCA Analysis
• [AZ-400] Monitor Azure With Grafana
• ServiceNow Integration With Azure DevOps
• Veracode Source Code Analysis
• [AZ-400] DevSecOps And Tools
• Rugged DevOps & DevSecOps

Next Task For You

Begin your journey towards becoming a Microsoft [AZ-400] Certified Azure DevOps Engineer and earning a lot more in 2020 by joining our FREE Class.

Click on the image below to Register for the Free Class Now!