Cybersecurity: Securing Your Infrastructure
System hardening, secrets management, OWASP, network segmentation and DevSecOps best practices. Reduce your attack surface.
- Identify the main risks
- Harden systems and configurations
- Secure the development lifecycle
- Adopt a DevSecOps posture
- Identify the most common weaknesses in your infrastructure and fix them with a priority plan
- Apply CIS Benchmark hardening to your Linux servers without breaking services
- Set up a secrets management policy that stands up to a security review
- Talk to a security team or an auditor: understand and defend your architecture choices
The programme
Day 1 - Posture & hardening
- 2026 threat landscape: ransomware, supply chain, cloud misconfiguration
- Linux hardening: CIS Benchmark, SELinux/AppArmor, auditd
- Secrets management: Vault, SOPS, rotation rules
- IAM and the principle of least privilege on AWS/Azure
- Workshop: server configuration audit with Lynis and remediation
Day 2 - Application & network security
- OWASP Top 10: injection, XSS, SSRF, deserialisation, in practice
- DAST scan with OWASP ZAP on a vulnerable application
- Network segmentation, Kubernetes NetworkPolicies, web application firewall
- TLS/mTLS, internal PKI and certificate management
- Workshop: guided pentest on a lab environment (DVWA)
Day 3 - DevSecOps & incident response
- Building security into CI/CD: SAST (Semgrep), DAST, SCA
- Docker image scanning with Trivy, Snyk and Grype
- IaC security scanning: Checkov, tfsec on Terraform
- Incident management: detection, containment, basic forensics
- Final workshop: complete secure CI/CD pipeline with a security quality gate
Who is this for
Ops, developers and engineers concerned with security.
Prerequisites
- System and network basics
- Development knowledge (an advantage)
Format
Frequently asked questions
Is the course eligible for OPCO or CPF funding?
No. Sphinx-Digital is not Qualiopi certified and is not listed on Mon Compte Formation. The course is invoiced directly to the company or the individual, with no external funding.
What is the difference between the public (inter-company) and in-company formats?
In the public format, you join a session with participants from other companies (3 to 10 people). In-company, we run a session dedicated to your team, on your site or remotely, with content adapted to your context. In-company pricing is available on quote.
Remote or on-site: what are the practical differences?
Content and labs are identical. Remotely, labs run on cloud environments accessible from a browser, with nothing to install. On-site, you provide the workstations; labs can run in the cloud or locally depending on your infrastructure.
How many participants per session?
3 to 10 participants at most. This deliberate limit ensures everyone can ask questions, adapt the exercises to their context and get a detailed answer.
What is the evening format?
The evening format spreads the same course over 4 sessions of 3.5 hours (14 hours in total), in the evening from 6:30 pm to 10:00 pm. Same content, same labs, same price, so you can build skills without taking days off.
How does payment work?
Courses are invoiced on quote, by bank transfer. Payment in instalments is possible. We issue a training agreement for companies that want their training department to cover the cost.
Interested in this course?
Join the next session or request a tailored in-company session.
What participants say
Not sure this course fits your context?
A 20-minute call to take stock before you enrol, with no sales pitch.