Skip to main content

Why I am Excited to Attend the DevSecOps Engineering Class

The opportunity exists to reinvent security and to do this we must redefine the roles and practices of security engineering. Information is available faster than the speed of your connection and cybersecurity risk is everywhere! 

Empowerment to change begins with getting level set on what DevSecOps (DSOE) really is and how to move fast to get there.  That is why I am excited to attend the DevSecOps Engineering class and to acquire the DevSecOps Engineer certification! 

Digital Transformations are not only real, they are accelerating. IT systems and software literally drive the world and that makes every business a digital tech business. Along with that is a proliferation of apps, devices and opportunities. Those opportunities are not always honorable; hackers abound. DevSecOps is a mindset that “everyone is responsible for security” with the goal of safely distributing security decisions at speed and scale to those who hold the highest level of context without sacrificing the safety required. 

As an IT professional, I want to be a part of THAT!

DevSecOps:
  • Ensures that security professionals are included as part of the DevOps team to helps Dev and Ops professionals understand
    • How their decisions need and affect security
    • How to work with security to decrease and respond quickly to attacks
  • Integrates security practices into the DevOps process and pipeline automation
  • Strives to automate core security tasks key takeaways

The opportunity exists to get your entire team and organization on the same page. Collaboration without education and training will not allow us to optimize at the level needed. We no longer have years and months to get the traction required. A DevSecOps, security as code, mindset is required now.

Shared practices are encouraged so I know that I will come to class ready to participate in lively discussions about, benefits, challenges and how to move people, process and technology for optimized DevSecOps.

Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th