The presentation discusses the importance of a privacy red team in addition to a security red team, and how to build and operate one at Meta.
- Privacy red teams focus on testing user data, while security red teams target the company as a whole
- Blue teams need to be aware of the activities of privacy red teams to avoid triggering alarms
- Meta's privacy red team conducts adversarial testing through adversary emulation, purple team operations, and product compromise tests
- Operations that can be performed include detecting sensitive data leaks and testing the accessibility of contact information
- The goal is to proactively identify and mitigate risks to user data and privacy
One example of an operation is testing the accessibility of contact information. Low-sophistication adversaries can easily access functionality that allows them to input or output contact information, making it important for blue teams to have detections in place. Another example is detecting sensitive data leaks, which can be caused by absent-minded developers who may unknowingly use external resources to process data. By conducting adversarial testing, Meta's privacy red team aims to proactively identify and mitigate risks to user data and privacy.