practical-devsecops.comReviews of practical-devsecops.com

The experience with the instructor was very thorough. All the preparation for the final exam was meticulous and with the right personal reading, it ensured your success in the final exam.

The lab courses and practical labs were useful. I liked how the course had set up a lab for the participants to play around. The courses are up to date and they are real world scenarios.

it was pretty good course and exam

I was one of the early "Alpha" or "Beta" students, and at the time, the course was still under development, with content released progressively—chapter by chapter. As such, I chose to wait until the course was fully completed before beginning. After the course was finalized, I received a follow-up email from Practical DevSecOps, which showed their effort in keeping early students updated. During my learning journey, I noticed that course materials were occasionally moved or updated. If you're planning to enroll, do be aware that the course is relatively new and actively maintained. The team frequently refreshes and improves the content, which is a positive sign of commitment to quality. Just keep in mind that you might see your course progress drop (e.g., from 100% to 90%) when new content is added—this is normal and reflects ongoing updates, not missing progress. In terms of content, this course is one of the few that offers hands-on, practical experience in this domain. Personally, I found it worth the investment. Although I later discovered a cheaper alternative, I have no regrets about choosing this program. Key topics I learned include: Building Large Language Models (LLMs) Implementing Retrieval-Augmented Generation (RAG) Checking for outdated packages and dependencies Detecting toxicity and evaluating model accuracy Most importantly: vulnerability scanning using a variety of tools, and applying appropriate patches Overall, it’s a solid course for those seeking hands-on skills in secure AI development and operations.

Great content, for beginner to mid-level DevSecOps engineers, exam could've been much better TBH

The labs were the difference makers. concepts got easy to understand using labs

I recently completed the Certified DevSecOps Professional (CDP) certification, and I found it to be an exceptionally hands-on and well-structured program that delivers both breadth and depth across modern DevSecOps practices. The course stands out for its practical, lab-driven approach. Rather than just theory, it dives into real-world tools and scenarios — including CI/CD pipeline integration, container security, static/dynamic analysis, Infrastructure-as-Code (IaC) scanning, and runtime security monitoring. Each module is supported with detailed walkthroughs, example scripts, and guided labs, which made the learning process not only interactive but also applicable to real environments. What I appreciated most was the quality and completeness of the training materials. The documentation is thoughtfully organized and rich with diagrams, code snippets, and tool comparisons, making it easy to reference even after the course. Whether you're new to DevSecOps or looking to strengthen your implementation knowledge, the materials provide a solid foundation. The certification reinforces security as a shared responsibility across development and operations, emphasizing automation and continuous security integration. Overall, it’s a valuable investment for professionals aiming to build or enhance secure DevOps pipelines in their organization.

Whether you are just bootstrapping your Supply Chain Security knowledge or working towards increasing the maturity of your org's processes this course is highly recommended! As with most PDSO courses, this was jam packed with materials, hands on practice, tool exposures, threat modeling, attacks & defenses, and related framework information. The coursework can mostly be tied to Code, Container, Cluster, and Cloud (aka “The 4C’s of Cloud Native Security). There were a ton of cool things in this course. All of the hands-on tool exposure is a given. Besides that, I found the concept of software provenance to be a nice escalation from the SBOM-centric state that the industry has embraced (particularly after log4j). It was also really cool to get increased exposure to frameworks such as SLSA, NIST SSDF, SCVSD, OpenSSF S2C2F, SCITT, DORA, and CII.