Just enough Security - Mary Gilmartin
26 Jan 2017
-
Locked
Talk Description
Ever read an article about a data leak and wonder if there is anything you can do as part of your testing routine to prevent that? While Security can be all doom and gloom, it turns out that Test can share more of the security burden in a way that’s agile and minimal. In this session I will introduce you to what you need to know to minimize the security risk to your organisation.
What they can do for any project that will improve security that does not involve any programming. Also some ideas of where to start with sprinkling security tests into automation.
By the end of this session, you'll be able to:
- Identify security risks that can impact
- Describe the dependency problem and related risks and how to mitigate them
- Identify approaches to security testing
- Relate the use of charters to security testing
- Describe the impact of time on the security risks
- Describe risks aroun data loss and breaches and how to mitigate them
- Describe the impact containment charter
- Identify the role of automation in security testing
Sign in
to comment
Suggested Content
Create E2E tests visually. Get clear, readable YAML you can actually maintain.
Explore MoT
RiskStorming; Artificial Intelligence is a strategy tool that helps your team to not only identify high value risks, but also set up a plan on how to deal
Gain the tools you need to become an operability advocate. Making your testing even more awesome along the way!
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.
