Become a better Software Architect by designing secure systems
InstructorMemi Lavi
Free
Free
Free
The curriculum integrates security principles across the development lifecycle, covering stages from SDLC processes to testing and production environments.
Dedicated sections cover threat modeling methodology and specific tools to help anticipate attack vectors.
Editorial course preview
These 4 complementary views highlight concrete, legible examples from the course presentation.
This diagram illustrates a Man-in-the-Middle attack scenario where an attacker intercepts a user's financial transaction and maliciously alters the recipient from David to John.
This slide visualizes the course structure using a concentric circle diagram that categorizes security topics into three levels: Completely Ignore, Be Aware Of / Recommend, and Decide and Design.
This slide defines software security by listing the four key areas it protects against: data loss, disruption of service, data leak, and data inconsistency.
This slide outlines the severe risks of a non-secure system, highlighting that it can destroy your reputation, kill the business, or lead to criminal charges.
One signal from before the displayed update identifies errors regarding OAuth2 as an authentication protocol and suggests incorrect practices for password storage and data integrity; note that the current update label does not prove these issues were corrected.
The content may overlook state-of-the-art variations like attack trees or modern authentication methods such as WebAuthn and Passkeys. One signal from before the displayed update suggests these are missing; the current update label does not prove a correction has been made.
The curriculum aligns with the goal of introducing security to architects and developers, but may not meet the needs of upper mid-level professionals.