See the system as an attacker might.
Explore assets, attack surfaces, and trust boundaries before choosing controls.
Security · In development
A dedicated path in development for engineers who want to understand threats, protect systems, and make security part of how software is built and operated.
Security
Build the future. Protect what matters.
This path is in development. The content below outlines our intended direction; the curriculum and project examples may evolve before launch.
The transformation
Every new application, cloud environment, and AI feature creates decisions about trust. Security engineers need to understand what they are protecting, how it could fail, and which controls matter. We’re developing a path that connects those questions to the systems engineers build and operate.
Explore assets, attack surfaces, and trust boundaries before choosing controls.
Understand identity, least privilege, and how services and people reach sensitive resources.
Connect secrets handling, dependency review, and cloud controls with the development workflow.
Consider what to log, how to recognize a problem, and what a useful response plan contains.
The intended experience
This is the proposed learning experience. The final program offer will be confirmed before enrollment opens.
The intended scope covers identity, cloud security, threat modeling, secure delivery, detection, and incident response.
Explore example system reviews that connect assets, permissions, data flows, and security controls.
The intended approach emphasizes clear threat models, prioritized remediation, and useful response documentation.
Proposed focus areas
Follow the connections between the tools, the decisions, and the system. Open a module to explore its focus and an example of the work.
06 connected modulesMeet Teleios LabIdentify valuable assets, trace data flows, and examine the boundaries between users, applications, services, and infrastructure.
Example practical outputAn asset inventory and trust-boundary map
Explore authentication, authorization, service identities, and least privilege. Understand how access decisions can reduce or increase exposure.
Example practical outputA least-privilege access design
Examine resource configuration, network boundaries, data protection, and the division of responsibility in a cloud environment.
Example practical outputA cloud configuration review
Bring dependency checks, secrets handling, and security review into the path from code to deployment.
Example practical outputA secure delivery checklist
Consider which logs and signals are useful when investigating suspicious activity and how to preserve an understandable record of events.
Example practical outputA logging and investigation plan
Connect findings to action: prioritize fixes, define a response plan, and document what a team should learn from an incident.
Example practical outputA response runbook and findings report
Teleios Lab / Project spotlight
Illustrative project direction: review an application and its cloud environment. Map sensitive data, investigate excessive permissions, and document how you would reduce exposure and respond to an incident.
Inside Teleios LabThe evidence of your work
A threat model and data-flow diagram
An identity and permissions review
A prioritized remediation plan
A security incident response runbook
An illustrative project, drawn from the curriculum’s focus areas.
Find your starting point
Builders interested in protecting applications and infrastructure, cloud practitioners who want stronger security foundations, and aspiring security engineers. Final entry requirements will be confirmed before launch.
A foundation for exploring cloud security, application security, and DevSecOps work. Final learning outcomes and program structure will be published before enrollment.
Stay in the conversation
This path is still in development. Pricing, teaching format, duration, and prerequisites have not been announced, and enrollment is not open.
Talk to us about securityExplore Cloud Engineering / DevOpsReview the proposed focus areas and project examples.
Share your background, goals, and the problems you want to work on.
Enrollment will open only when the curriculum, format, and pricing are confirmed.
No. This is a preview of the intended direction. The dedicated program is still in development and does not accept enrollment or payment.
The current direction focuses on identity, cloud and application security, threat modeling, secure delivery, and response. The final scope will be announced at launch.
Cloud Engineering / DevOps and Fullstack Engineering are available now. Both offer useful context for understanding how systems are built and operated.
Use the Get Involved page to share your experience, interest in mentoring, or the security problems you want to learn to solve.
Your work starts with a decision.