You're reading from CompTIA Security+: SY0-601 Certification Guide Complete coverage of the new CompTIA Security+ (SY0-601) exam to help you pass on the first attempt

Product type Paperback

Published in Dec 2020

Publisher Packt

ISBN-13 9781800564244

Length 550 pages

Edition 2nd Edition

Languages

Python

Tools

Kali Linux

Concepts

Cybersecurity

Author (1):

Ian Neil

View More author details

Table of Contents (24) Chapters

Preface

1. Objectives for the CompTIA Security+ 601 exam

Exam Objectives (Domains)

2. Section 1: Security Aims and Objectives FREE CHAPTER

3. Chapter 1: Understanding Security Fundamentals

4. Chapter 2: Implementing Public Key Infrastructure

5. Chapter 3: Investigating Identity and Access Management

6. Chapter 4: Exploring Virtualization and Cloud Concepts

7. Section 2: Monitoring the Security Infrastructure

8. Chapter 5: Monitoring, Scanning, and Penetration Testing

9. Chapter 6: Understanding Secure and Insecure Protocols

10. Chapter 7: Delving into Network and Security Concepts

11. Chapter 8: Securing Wireless and Mobile Solutions

12. Section 3: Protecting the Security Environment

13. Chapter 9: Identifying Threats, Attacks, and Vulnerabilities

14. Chapter 10: Governance, Risk, and Compliance

15. Chapter 11: Managing Application Security

16. Chapter 12: Dealing with Incident Response Procedures

17. Section 4: Mock Tests

18. Chapter 13: Mock Exam 1

19. Mock Exam 1 Solutions

20. Chapter 14: Mock Exam 2

21. Mock Exam 2 Solutions

22. Chapter Review Solutions

23. Other Books You May Enjoy

Understanding Secure Application Development, Deployment, and Automation

There are two main models of the Software Development Life Cycle (SDLC), the first being an older version that is called Waterfall, where each stage is completed before the next stage commences. This is known as a cascade model. The newer, faster, and more flexible model is called Agile, which is similar to Scrum, where several stages of development can occur simultaneously. Agile is customer-focused, and each part of the project is called a sprint that has many tasks assigned to it. If you have three stages, then there are three sprints. Say each sprint has three tasks. The project concludes when all tasks within each sprint are complete, making that sprint complete. The whole project is complete when all of the sprints are complete.

Before applications can be used in a production environment, we must ensure that they are as secure as possible so that we mitigate the risk of being attacked by an outside agency...