Today we are joined by Kim Wuyts from KU Leuven, to talk about privacy threat modeling. We will start by discussing what LINDDUN is and the difference between privacy threat modeling and security threat modeling. We will then discuss how a framework like LINDDUN can be used in DevSecOps pipelines as part of an evolving knowledge base. For those who wish to provide feedback to the LINDDUN team, Kim will share some ways that you can reach out to her team. Privacy is a critical part of our software that is often neglected. With new regulations and standards emphasizing both privacy and security, we need a consistent approach to help guide policy creation and software development activities.
Developer-centric Threat Modeling
Continuously model threats at scale and proactively write code that significantly reduces risks and remediation costs.
Our services help enterprises meet compliance requirements and raise security standards. We offer eLearning courses in application security, operation security, and compliance that teach secure software development principles to development teams, in addition to general security awareness suitable for non-technical learners.
- Contact Us
- Book Demo
- Mobile Only