48 min

Privacy and the creepiness factor of collecting data

With Chris Romeo, Izar Tarandach, and Matt Coles

Privacy & data protection

What is privacy, and how does it intersect with security? We are joined by our first guest, Ally O'Leary, a privacy compliance expert.

Episode title image: Privacy and the creepiness factor of collecting data

Listen to the conversation

About this episode

What is privacy, and how does it intersect with security? We are joined by our first guest, Ally O'Leary, a privacy compliance expert. Ally works for a consumer electronics company, ensuring compliance with global privacy laws and acting as a data protection officer.

The episode delves into the intersection of privacy and security, with Ally explaining how these two areas often go hand in hand. She emphasizes the importance of understanding the definition of personal information and being aware of where such data is stored within a company's systems.

A significant part of the discussion revolves around why security and privacy are two different functions within a company. Ally explains that privacy is a relatively new concept for most companies, often triggered by regulations like the GDPR. She also mentions that privacy often becomes part of the legal function due to the close work with attorneys to interpret laws.

The conversation also touches on the challenges of data governance and the importance of proper data ownership on the business side. Ally highlights the need for regular reviews of data flows and audits to stay on top of data governance.

Towards the end of the episode, Ally advises security professionals on when to involve privacy experts in their processes, especially during the development life cycle. She encourages security professionals to notify their privacy colleagues about any projects or initiatives that might impact systems containing personal data.

Overall, the episode provides valuable insights into the world of privacy compliance, the relationship between privacy and security, and the role of data governance in protecting personal information.

Follow AI Security Table:

➜ Home: https://securitytable.ai/

➜ X: https://x.com/AISecurityTable

➜ LinkedIn: https://www.linkedin.com/company/ai-security-table/

➜ YouTube: https://www.youtube.com/@AISecurityTable

Transcript · 48 min conversation

0:09Chris Romeo Hey folks, welcome to another episode of The Security Table. This is Chris Romeo, and I am as always pleased to be joined by my friends, Izar Tarandash and Matt Coles, as we sit and ruminate around the security table. Well, this is kind of a momentous occasion for us. We have our first ever guest. And no, it's not because this is the first time someone actually agreed after many, many efforts we made to try, we've been begging and asking and pleading. No, no, no. We're super excited to have Aly O'Leary with us, who I'll let Aly tell you what she's, what kind of her expertise and everything is.

0:49Ally O'Leary Yes. Hi, thank you for having me. I'm very excited. So I work in privacy compliance for a consumer electronics company, and it's my responsibility to ensure the company is in compliance with global privacy laws. So we have a global privacy program, and we've got a small team that works for me. And I'm also a data protection officer, which I don't know if you guys are familiar, familiar with that role, but a lot of privacy regulations require that role, which in a nutshell is someone who's supposed to remain independent and always be thinking about the individuals whose data you're collecting— employees, consumers, whatever it is. To make sure that you're honoring their rights and their freedoms. So you get to kind of remain an independent person that gets to kind of poke at what folks are doing and see if it's actually the right thing on behalf of those folks. So that's what I am. And then prior to doing— I've been in this role for about 5-ish years now, but prior to that, I did a brief stint in security. Um, so I have a, not a vast knowledge of it, but privacy and security go hand in hand. So having that kind of little bit of background has definitely helped me in my current role today.

1:54Izar Tarandach So many questions.

1:56Chris Romeo Yeah, me too. That's what I'm thinking. It's like so many things I want to ask. Where do we even begin? All right. So, we talked, we want to focus our conversation in the world of privacy by design. So, between Matt and Izar and myself, we spend a lot of time thinking about software applications, hardware developers, building stuff is, is something that, that we all spend a lot of time thinking about. And so when we think about privacy by design, I feel like this is something I don't know enough about. I'm just going to put that on the public record here. And so maybe you could start out, Allie, just by laying a foundation for us about what is privacy by design, why do we care about it, and kind of let's see where we— let's see where we go from there.

2:43Ally O'Leary Sure. So it's, it's based on the same principle as secure security by design, which is you're always— their privacy of the individual is not an afterthought. So you're always considering it and developing requirements throughout the entire development lifecycle. It's not something you're— all the requirements you're thinking of at the beginning of the project, and then maybe at the end you come back and make sure they're right. Now you should be having that conversation throughout the whole time. And so some things that you have to think about are the legal and ethical considerations when it comes to collecting personal information. So, um, and most privacy regulations have the same set of standard privacy principles, which are, um, notice and consent, making sure people are aware of the data you're collecting. And that you get consent to that collection if needed. When you collect that data, you need to have a specific purpose and use for collecting that. You just can't collect all of this data and then decide, oh, we needed this, these elements now, but later we want to collect these other data elements because we might use them a year from now. So I have a lot of conversations with security— not security, sorry, IT teams too, to kind of vet the different data elements they're going to be collecting. So that gets at the data minimization principle of most privacy regulations. Also the entire data lifecycle management. Most people like to collect data, but they don't like to think about once they're storing it, one, how they secure it, but two, how long are they gonna keep it? How long, when, when are they gonna delete it? Data gets stale all the time. We should be thinking about that. The rights of individuals. So individuals have the right in some cases to get a copy of the data a company holds on them, to delete that data or even update that data. And you have to build in processes for those. And a lot of the time you have to build that as you're building the system. And then another thing that is always a consideration— there's a number of things, but the big one too that's helpful at the beginning of a project versus the end is something called a cross-border data transfer. So if you're collecting data from an individual residing in one country and your IT system happens to be in another country and you're going to store it there, there are actually some requirements when it comes to where you store that data. And so of course you'd like to have those conversations up front or along the way because there are times where the IT teams have decided we're going to store this data in the US. And then at the end of our project, right before they go live, I don't want to come in telling them, sorry, no, and now you have to do a bunch of rework. So it's one, all about ensuring the privacy of the individual, and it's always the forefront of the actual person you're collecting the data on, but also making sure the company is in compliance and there's no rework that these poor IT or software teams have to deal with.

5:11Chris Romeo Yeah, and that's something we're, we're always happy to hear on the software side is being able to minimize the rework. I can say, you know, from my privacy— call it a privacy journey— I encountered privacy in the kind of with GDPR. So building a product, having a startup that was building a product, bumping up against GDPR and the— what was the thing that they called that was the thing we could sign up for? Privacy Shield, the thing here in the US that was supposed to cover us. So that was really my exposure to privacy. I'm curious from from Isar and Matt's perspective, like what— now that we've got this kind of foundation of privacy by design and the things that privacy are doing, what's been your experience, Matt and Isar? Have you worked with privacy teams before kind of in trying to solve the problems that Ali's talking about here?

6:03Izar Tarandach Matt, you go first because I'm going to take this somewhere completely different.

6:10Matt Coles Yes. So first off, I'll level set that Ali and I have worked at the same consumer electronics company. And so, I do have some experience with working with my peers and partners in privacy. It is definitely a different mindset and definitely an interesting tug of war, I guess, between who owns what and who does what. But in the end, obviously, security has to be able to support privacy because you can't have privacy without security. Although I imagine the reverse is not true. And actually, I wanted to get your opinion on that. You know, you definitely— I think you cannot have privacy without security, but can you have security without privacy?

7:01Ally O'Leary When the data is not personal information, sure. I don't necessarily care about highly confidential IP data that a company may have, and you need secure that. But if you guys are securing personal information, you can't not have privacy rules associated with it.

7:18Chris Romeo Is that—

7:18Ally O'Leary it's like, I view it as a Venn diagram, right? Security is very focused on the requirements associated with very, the very important data that a company or whatever has. Privacy is focused on a narrow set of that data, personal information. But we're more focused on, like I said, those legal and ethical considerations. With use, collection, storage, the whole data lifecycle. And so really the Venn diagram is the security of that personal information, or that's how I view it at least.

7:45Chris Romeo So, let me throw, let me just, before I use our ghost and he's gonna take us in a different direction, but I have a similar direction, but I think this is a bit, could be a bit of a controversial question. So, that's why I'm gonna throw it out on the security table because that's what we do here is throw controversial things around and see what happens here. Why is security and privacy two different functions then inside of a company? Why are these things not combined together? Why don't we have a single group that serves both of these purposes together?

8:16Ally O'Leary That's a valid question. Yeah, and I will say, so I will, most companies privacy is new and most companies it was the GDPR that forced companies to stand up a function. So what I will say a lot of folks I've talked to, privacy ends up being in the legal function, just because you have to work so closely with attorneys to interpret the laws. And it's just a de facto, let's throw them in this organization. Other cases, it ends up being folded under a security team in a GRC function as well. I don't think one, unless you're like the big players like Microsoft, I don't think one company has really figured out the best way to do it. And I would argue too, the same problem exists with data governance and understand like the teams that are responsible for ownership of data, data flow, data flow diagrams, all three of the security, privacy, and data governance all kind of fit together. And I don't know if any— there's no one right answer. I don't think I personally have never experienced any fighting though with security and that where we've had to go to our different management streams and we've had to like fight over something. We've always worked things out. So I'd be interested if you guys have other experiences in that regard.

9:23Chris Romeo I can't say I have knowledge of any fights between them, but it was— it's just always— it's always been for me kind of Just one of those things I look at and go, why are these things? Because the people you're trying to influence, at least from a privacy by design perspective, are the same engineering teams. One of the things like, and I'll reference my time at, I'll just say where I worked because everybody knows Cisco. So, I worked at Cisco and one of the pushbacks we would get in regards to security even was product teams would say, 'You're coming at us from 27 different directions. You got to get your story together. Come at us from one angle. We want to do the things you're preaching and prescribing for us. We think they're a good idea, but you're sending 27 different streams at us simultaneously, and we have to dedicate individuals just to manage all of the noise coming from you.' And so, when I think about security and privacy being one stream that could go to the engineering team potentially to save additional overhead. But it seems like from your perspective, they're coming from— you're kind of— you're sitting under the legal function, or used to privacy teams sitting under legal, and security teams— I don't think I've ever reported to legal. I've never seen a company where security reported to legal.

10:38Matt Coles Actually, our— the company I work for, the company I work for now, our security team is under legal.

10:44Izar Tarandach So it turns out that if I wait enough, I don't even have to take things to another different direction because somebody else is going to bring it around.

10:52Matt Coles So, oh, is that where you're the bombshell you were waiting for?

10:54Izar Tarandach Yeah, yeah, no, no, you guys sprinkled the grenades when I was playing with the, with the nuclear bomb. But, uh, the thing is, the other day I was working at this place and, and of course one of my, my tasks was to like train people, raise awareness and all that good stuff. And one of our engineers caught me at lunchtime and told me that, uh, his manager had turned to him. The guy had been doing a governance and, and and stuff like that. And he said that his boss turned to him one day and said, "Mazel tov, now you are a privacy engineer." And he looked at me with like puppy eyes and said, "Could you please tell me what the hell is privacy?" And it seems to me like we are just assuming since we started talking that everybody knows what privacy is. Can you please give me a definition of what privacy is?

11:45Ally O'Leary Yes, um, I would say in layman's terms it's the creepiness factor of whether or not you want to collect all this data on individuals and what you want to do with it. That's like the simple— if I had to tell my sister, but that, that's how I would explain it. But, um, it really comes down to our legal obligations and then your ethical considerations for when you want to collect data and what you want to do with it. Um, and that's why it's all about the data lifecycle management. And I know you guys are talking about, um, Chris, you were just talking about seems like everyone's going to the same teams with the same requirements. And that is true. So I have a couple of comments about that. Um, there are different, obviously, gates and checkpoints in the software development life cycle that I think it makes sense that you have both a security and a privacy person in those meetings as part of those same conversations. It— that makes complete sense. And then, but I also think, I'm not sure you guys— security necessarily works with at the business function, like business process, for example. Sales initiatives, marketing initiatives, those are all collecting data, but it's not necessarily a new system that we have to make sure have security requirements implemented in them. So I actually have to talk with those people, understand their business processes and talk to them. Well, how are you planning to use this data? And then also once we have the data and it's secure, how is this other group gonna use the data? Have we disclosed that use to our customers? Do people know we're gonna use, can we even use the data in that way? So it's a matter of really I'm more concerned about use of data and the spreading of data and who has access to it for that purpose.

13:13Matt Coles So, so would you say, sorry, would you say that so security is focusing on primarily technology stacks and, and some process, whereas privacy is focusing on people and functions and processes?

13:29Ally O'Leary Yes, I think that's accurate.

13:31Chris Romeo It's, it's always like, it's funny to think about this, like So when we're attached to the engineering team, sales calls us and we're like, my phone is, my phone is apparently is not working. My, my Slack or Teams.

13:46Izar Tarandach I'm going into a tunnel.

13:48Chris Romeo Yeah, I'm going into a tunnel. And that's kind of our general, our general approach is the, and, and it's, it's always funny because there's every place I've been, there's always been this weird, this weird kind of relationship between engineering and sales. And I don't even know why it always exists. Like, I don't know why people are always like, oh, it's sales, you know, come on, don't even— you know, we don't want to talk to them. But it sounds like from the privacy perspective, like, you're thinking about all the things that salespeople are typing into their BlackBerrys— yes, I said they're BlackBerrys— and storing somewhere into, into, uh, some data source somewhere. And so yeah, that's a— it's an interesting perspective. And Ali, that's one that I've never thought of, and I didn't realize— I never realized and thought about, oh wait, you have more than just the software pipelines source control systems contents to worry about. You have all the things that salespeople are doing along the way.

14:40Izar Tarandach So now that I know that privacy is basically the creepiness factor of data, my next question is, Chris said, can there be privacy without security or security without privacy?

14:53Matt Coles I asked that question.

14:53Izar Tarandach You asked that.

14:54Ally O'Leary Sorry.

14:55Izar Tarandach And now I am going to scope that down. As we know, security likes to say that we have these like top values that we try to work with. CIA, confidentiality, integrity, and availability, and I want to focus on confidentiality. Can you have privacy without confidentiality and confidentiality without privacy? How do the two values link? Do you see them in the same level today? Meaning now we have CIA-P, or is P still growing up?

15:28Chris Romeo P is silent.

15:30Izar Tarandach P silent.

15:32Ally O'Leary So it's, it's interesting because obviously if you hold personal information about consumers, employees, whatever it is, you need to keep that confidential. And that, that should— there are rules around how you protect that and keep that. But there are other scenarios in the privacy world where you— companies may want to scrape publicly available data out there that might not actually be confidential data. And so and you scrape that possibly to— and there are privacy considerations around scraping data anyways, but you may want to use that for marketing initiatives or to segment and profile people and things like that. So once you bring it in-house and now you're kind of tying it to individuals, then it becomes confidential. So I think it's still part of that confidential umbrella. I would love for a silent P. Obviously, I'm always advocating for privacy and learning more and more people to learn about it, but I think it ultimately does fall under the confidentiality.

16:29Matt Coles Well, can we extend that question actually a bit then also with, let's not leave out I and A in those conversations. So, if confidentiality evolves as you go from just simply data to now data that is scoped within privacy, what about integrity and availability? If I recall, there's something around loss of data that you hold on a user. Is that really a privacy problem or is that really a security problem still?

17:04Ally O'Leary Hmm. Both, because if you lose data, then you're at risk of, you know, having significant breach. And breach is very specifically defined within regulations and has obligations. You have to report to regulators within a certain time period. You may have to notify the people who you have their data has been lost. So, um, it's hand in hand, but there are so many more legal obligations that— don't, don't lose the data. That's what I would say. It gives me heart palpitations just talking about it.

17:36Matt Coles Well, this— I mean, losing data from a data breach though is, is arguably confidentiality, not availability still, right? If somebody else steals the data, it— you, you violated confidentiality.

17:48Ally O'Leary Okay.

17:48Matt Coles If somebody— if a company owns— has all— has data on a person and they delete it by accident, its availability, correct?

17:59Ally O'Leary Yes. And I mean, do you— yeah, you'd have to think about it. So go ahead. No, I didn't want to get—

18:05Matt Coles no, you finish your— finish your thoughts.

18:07Ally O'Leary You'd have to think about—

18:08Matt Coles this is what we do here—

18:09Ally O'Leary the significant effects of losing that data to the individual. So for example, you are, uh, a healthcare company who has now just wiped out all of my medical records. That's going to have a significant impact on me and my ability to get services. But if, uh, you have accidentally wiped out my Twitter account, it's not that big of a deal. I can recreate the account again. So I think it more becomes a risk-based factor. And well, you might argue that—

18:36Matt Coles People that tweet, they get on Twitter. Can't get that blue checkmark back, you know?

18:41Ally O'Leary And so— So I think it comes down to a risk-based decision about the type of data you have and whether or not it's available or not. There are other arguments, right? So you have certain rights I mentioned earlier. We can get a copy of your data to delete your data, update your data. If you don't give me the ability to get a copy of my data because you've wiped it out, sure, you could have some legal implications there too. So, um, you're right, all three, the CIA, they all apply. Integrity too. You have the data has to be accurate and based on what you know about me, it has, should be, it should be accurate and yeah, there should be good quality data. Yes.

19:18Matt Coles So, I'm gonna ask, I wanna ask, I need to ask the question here, because it was initially confusing and then it was just a point of interest. When we talk about personal data and maybe thinking about GDPR and the various other schemes that are now popping up over the place, you know, every state seems to be coming out with their own. Seriously, are email addresses really personal?

19:43Izar Tarandach Good point.

19:45Ally O'Leary So from a legal perspective, the answer is yes. I know you're saying like everyone's email address is out there in the wild. That's probably where you're going from all of this. But if you were to look at it—

19:53Matt Coles It's also what we use almost universally for all authentication systems.

19:57Ally O'Leary Yeah. Mm-hmm.

19:59Izar Tarandach Plus the schemes are well known. Like you always know that it's [email protected].

20:06Ally O'Leary But you're tying that email address to a lot of other data that you have on this individual. And the moment you take that one identifiable piece of information and tie it to all that other information, it all becomes personal data. And then it just comes down to all the requirements under breach notification laws that basically say if you have email address plus X, Y, and Z, now you need to notify. So it's, it's definitely personal information from my perspective.

20:29Chris Romeo Let's not forget, because I'm— let's not forget real quick, there are a number of email addresses people created like at Gmail that are super embarrassing when they're adults. And so we want to make sure those are, you know, super private and, and that those are protected because You know, I'm trying to think of one.

20:46Izar Tarandach What we want to be private here is the relationship, not the identifier itself. Like, the string itself doesn't mean much. What, what means is the relationship between that string and the rest of the data or the person. So it's not like the email itself, by string bytes stored, has some special value of privacy.

21:09Chris Romeo Or you just mentioned something that I just happened to scan Linden because, Ali, we're all good friends with Kim Voight.

21:16Izar Tarandach Linkability.

21:17Chris Romeo Linkability is— I think that's what you just described. I was like, I think Izar just used something from Linden because I was just looking at it a second ago. So, Ali, so what, what, like, give us a little more context on linkability. Like, in Izar's example here, it's the, it's the connectivity to the person that we're most concerned about, not the string of of bytes and values?

21:40Ally O'Leary Yes, I— it all comes down to identifiability. If you are able to individually identify a person through the data, then yes. And that's why you'll see there's always going to be— this is where privacy fights with development teams, where, um, you have direct identifiers and indirect identifiers. So direct identifier: name, email address, things like that. And then indirect identifiers like IP address, other things. There's a big argument in the world about whether or not cookies are personal information, but because It can all be tied and directly connect to one another and you can make observations and you can either profile people based on that data or understand their browsing habits and all sorts of things like that. It's all personal, all personal information that could either feel invasive, like you're monitoring them, like you're making automated decisions about things that they've done. So linkability and identifiability as well.

22:31Matt Coles So this is where the conflict I think comes in between security and privacy. Right? So let's take authentication as an example, right? If we're going to use email addresses as the source of identity for a system, so you're going to use your username as your email address. In security, we're going to ask you to— that obviously we want to protect the interface that we use for authentication so that credentials can't be stolen, but we're going to want to make that association between a username and a credential. And a username and their set of roles. And we're going to log any attempt at authentication by writing who tried to do what, which means writing their username to the log. Now all of that becomes in scope from a privacy standpoint, but we can't not do that, right? We can't not collect that data because if we don't collect that data, we lose all the security capabilities. But by doing so, we now have legal implications.

23:29Ally O'Leary So here's what I like to say about that. It's not that you can't collect data or do anything with that data. It's just a matter of making sure we have the appropriate controls and other things in place. So for example, most privacy laws— all privacy laws say you have to collect data and have a use for that data of why you've collected that. And in order to retain that data, you also have to have it. And for example, security purposes is one of those legitimate reasons why you can retain data. And things like that. So security plays a big point in all of this and how you can collect and use data or justify the argument, at least.

24:04Chris Romeo I have another bombshell question just to throw out on the table here, try to mix it up even some more. Should we institute a GDPR-like piece of legislation here in the United States? Ooh.

24:22Ally O'Leary Wow. Wow. Boom. Do you want me to answer that first?

24:26Chris Romeo Please do, because I actually do, I do have, I do have strong opinions about this as well, but I'd love to, I want to understand your, your perspective first.

24:35Ally O'Leary So as the average consumer, hell yes, is what I, am I allowed to swear? Um, I absolutely, I wish I lived in Europe right now. As a privacy professional, I will also say Hell yes, because as someone who needs to interpret all these— now we're up to, I think, 10 or 11 different state laws. They're all different and they all have different varying degrees of, um, strictness too. And so it's almost like, oh man, I wish I lived in California now, not Florida, for example. And so as a privacy professional, it's very hard— not hard, it makes it more complex to digest all the requirements and make sure your program— because most companies operate globally or across the United States is in compliance because there's just too many different states. So it would be great if we had one GDPR-S that kind of consolidated all of it. And if I had to request it right now, California has the most strict privacy laws, so it should be based off of California, in my opinion.

25:27Matt Coles Do you have a good example of any conflicting privacy laws?

25:31Ally O'Leary Not conflicting, just weak. Like, oh, like, why even put that into effect? Like, it's just not even doing any good in my mind.

25:42Chris Romeo So, Izar, what's your take? Do you think we should have a GDPR for the US, like a version of, a like version that we have across all 50 states?

25:54Izar Tarandach What could possibly go wrong?

25:59Matt Coles All 50 states and the District of Columbia.

26:01Izar Tarandach Yes.

26:01Chris Romeo Sorry.

26:01Izar Tarandach Or now we have to start litigating every single new piece of data that we want to collect and store and save and protect. Use and whatnot. And as we know, everybody around here loves a litigation. So yeah, do we want that added? Or do we want to do the right thing because it's the right thing to do?

26:25Matt Coles Why would we ever want to do that?

26:26Izar Tarandach Because we don't want the creepiness.

26:29Matt Coles We don't want to be creepy. We don't want to be creepy. Now, where's this all going to go? So first off, right off the top of my head, I'm thinking every credential data breach Every credential theft is a privacy violation. Large language models and other things are just going to make this infinitely worse. Having inconsistency of regulation across just the United States is very, very bad in these cases.

26:59Izar Tarandach Good boy.

26:59Matt Coles Especially when we talk about cross-geographical data transfers. Maybe the question isn't, do we need a US GDPR, but do we need a global GDPR? And I'm using GDPR as a placeholder for a privacy regulation. How do you get global PR?

27:16Chris Romeo Global anything though? Like ISO. Come on, ISO.

27:21Izar Tarandach For a second I thought that he was going to say that he was using global as a placeholder.

27:26Matt Coles Well, I want to leave, I want to leave room for Mars and the moon, right?

27:31Chris Romeo So I mean, Elon's, Elon's going to take us there. So, but I mean, ISO, ISO is a standard. Like, give me an example of where ISO has done anything on a global scale that was that was super positive that I'm going to get excited about here?

27:45Matt Coles Oh, ISO 27001 positive.

27:47Chris Romeo No, no, you didn't hear the rest of the question. I said that I'm going to get excited about like, I mean, what is ISO 27001 really done for the world?

27:58Matt Coles It's only created the underpinning for the entire information security space.

28:01Izar Tarandach Why do I feel like I'm in a scene of Monty Python's Life of Brian?

28:04Ally O'Leary It's so—

28:05Chris Romeo hold on.

28:11Matt Coles What has ISO ever done for us? I'm gonna say, what has—

28:16Chris Romeo It's the underpinnings of the information security.

28:22Matt Coles Everything refers to ISO, right? So ISO is the uber standard.

28:26Chris Romeo Everything what? Everything what? I don't refer to ISO. So if you look at—

28:29Matt Coles that isn't false. You don't refer to ISO directly, but presumably you use things like NIST 800-53.

28:37Chris Romeo No, because I'm not a federal government. I don't provide services.

28:41Izar Tarandach I have to be honest here. I get fascinated every time that Matt starts declaring and declaiming ISO numbers. I have no idea if they're right or wrong, but it's amazing that the number of numbers that he knows of ISO documents, like, it floors me every time.

29:00Ally O'Leary Okay.

29:02Matt Coles So, I will go out on a limb and suggest ISO, certainly ISO 27000 series C provides a common base for a lot of the things that we refer and rely on today, even if we're not using ISO directly as a reference.

29:19Chris Romeo But what teeth does it have though? Like, I can create an ISO standard and I can get a bunch of people to agree. We can have a meeting and we can make a standard. I can't make it enforceable. There's no enforceability to it though.

29:31Matt Coles Well, so there are complaints. There obviously are complaints. People love taking, taking other people's money, right? So there are complaints.

29:39Chris Romeo Be careful, be careful. Go ahead. What? It was a joke.

29:44Matt Coles That was a joke. Uh, so, so obviously you— so not obviously, there are some ISO standards that have no teeth. I'll give you example, ISO 27034. It's in the 27000 series. Is that the information application security related?

30:00Chris Romeo The SDL one?

30:01Matt Coles SDL, which is basically entire entirely, you should have a standard and you should follow that standard, but we're not going to measure you on the following of said standard. So, there are ISO documents that provide preferences, and then there are ISO documents that provide measurable compliance-based things. Now, what makes them— what makes them want— people want to measure against them is other regulations and other requirements and other standards that say measure against X, right? So, 27001, for instance, is sort of the superset set of controls and processes for managing information security management systems. There are various regulations across the world that then refer to ISO 27000 series as the reference point, and not just 27001. So if you look at NIST 800-53, for instance, as a set of controls, those controls implement implementations of things that are found in 27001. And if you look at many of the other standards as well that we refer to, the Cybersecurity Framework, for instance, the SSDF, those all, COBIT and other things, all have relations to ISO standards.

31:23Chris Romeo Okay, I want to go back. I want to bring Allie back to the conversation because we kind of went off on a bit of a rant here of Well, I can add to that.

31:31Matt Coles If you had just taken my statement as is, you would have been fine.

31:33Chris Romeo I mean, I still don't agree with where you landed, but I'm just being— I want to be polite to our guests and I want to get— I want to try to answer this question about how, like, could we make it a global standard for privacy? Because I'm not opposed to it. I just don't think ISO would do that. I don't think it would get us there. That's a whole— we can continue arguing that for the next 10 years. But Ali, from your perspective, like, what— like, how would we do this on a global scale? Like, could we do this on a global scale?

31:58Ally O'Leary I, I think the simple answer is no, and it comes down to, um, other countries not trusting the US. So they— a lot— the one I was talking earlier about, the data transfer, and the worry is that if we transfer data to the United States, do current US laws allow, um, other— like, allow the government to get access to that data under FISA orders and other things like that? And so that's why people are nervous to send their data of European citizens, China citizens, and have it stored in the US. So that is For example, right now I'm working to get in compliance with the China Privacy Law, and we basically have to justify to the Chinese government why we're allowed and if the data is okay to be stored in the US, for example. So I don't— and I just think China would never get on board with the same requirements around data that the US would have. So I just, I don't think it's practical. But, and then before I don't want to lose the thought I had when Matt was bringing up ISO, what I will say is if, um, you, if a company has an ISO certified or, or a security program based on ISO or another industry leader in ISO ISO, I will say, is the industry leader globally, and a regulator is inquiring because you've received a complaint or you have an issue, and you say, "We're ISO certified," they kind of walk away. They're like, "Oh, great. That meets the adequate security safeguards of our law," which is very basic. And so, I would argue ISO is actually valuable from that perspective in terms of the argument, if you had to.

33:21Izar Tarandach But now comes the question, okay, so before we go doing global policies and global policy? Is privacy a global value? So what they decide that is private data in China and here, is that the same data?

33:41Ally O'Leary Generally speaking, actually, yes. If you were to actually look at the definition of personal data across our global regulations, they're nuanced a little bit here or there, but yeah, I would say yes. But I think it's the perception of the individuals in those countries. So for example, in China, I think you would argue the average person doesn't— they don't anticipate having any privacy because of the government they have. In Europe though, they're very much, oh yes, and thank you GDPR because you're now forcing international companies to honor our respect. And then in the US, people are like, eh, we just assume everyone has our data, it's fine, not a big deal. So it varies.

34:15Matt Coles Oh, okay.

34:19Ally O'Leary But that's why I do have difficult conversations, for example, with our marketing teams, because it's, it's the, the mindset of how you— where you work. In marketing, they want all the data because because they want to be able to profile and get everything. And in their mind, because they market, they know other people have all their data, and so it's not a concern. But I think it's the same probably in security, right? You innately assume a platform is insecure, so you are cautious not to put your data in there or use it until you've done some due diligence. So I just think it's a mindset of how you— what data you value of your own. It's definitely— it's a personal mindset influenced by maybe what you do for work, or if you've been breached before or things like that. And it definitely varies by country or region. Yeah.

35:01Izar Tarandach Yes.

35:01Matt Coles See, a word of caution.

35:04Chris Romeo Let me translate. Hold on real quick. He just, the dog just said ISO is not the answer.

35:09Matt Coles Actually, on that point, I just looked it up. ISO 27701 is the privacy management standard. And three-quarters. Privacy information management standard.

35:22Izar Tarandach So, Annie, I have a question for you, and this is going to be a bit strange because perhaps you— Another word from our sponsors. Is it data? I hear a dog. Okay. So anyway, my experience with privacy lately has been that at some point somebody woke up and said, hey, we need the privacy effort and whatnot. And as you said, marketing loves collecting data and have been collecting all the data for all the time. And it's all over the company. Nobody knows who owns, nobody knows where it's stored, nobody knows systems, all that stuff. So we decided that we needed to look into a system that would let us take some control of data. And of course, we saw the different options out there. Many of them had agents and things that went into your cloud environments. Started going through your database and what these are. And at some point they stopped moving their hands in the air like I'm doing right now, very fast, and say somebody has to go and tag the data. So from your experience, what, what are the solutions out there that people could— without vendor names, what are the approaches for that kind of challenge?

36:34Ally O'Leary It's funny, I was on— I was participating in another kind of like a privacy forum where the same question was raised, and we were in fact talking about vendors. And it was a smattering of smaller companies and bigger companies participate in the conversation. And the answer is no one company has figured it out. They are either doing it all manual or they have a hodgepodge of this vendor, this vendor, and this vendor because no one vendor does it all for them. And even still, there's still, there's no thing called automation. You still have to have a human looking at stuff, tagging things, validating things, making sure there aren't any false positives. So unfortunately, it's really good marketing, I think, on the vendor side. And then when you actually get the tool, it's still too new, I think. I think data governance tools in general are still too new in the industry.

37:18Izar Tarandach Is it too new or is it inherently too subjective for us to be able to put rules into place?

37:26Ally O'Leary That's fair, especially when it comes to tagging personal information. Like I said, it's the indirect identifiers that get people hung up. Those are hard to identify, especially if they're not connected to other data. You could have data that's pseudonymized versus anonymized versus not. And so, it's more of a generic tag of, did this table maybe contain personal information? Let's do that. Because here's the reality. If I— we'd love to have all those data flows. If you have an incident happen, yes, it'd be great to reference those data flows, but I'm going to be calling people directly to tell me exactly, because I'm never going to trust those data flows or those diagrams or their systems because things change so often. That data changes so often. I feel like data feeds are not reliable. Ownership of the data changes, and new systems are added that are never actually incorporated into those systems. It's just you have to be really confident, and I'm not sure— I haven't met a company that's been really confident in their processes to date.

38:26Izar Tarandach What could be done to raise your confidence?

38:33Ally O'Leary A big data governance team, proper ownership of data on the business side, proper roles and responsibilities of what it means to own data, be a steward of data, I would say. And regular reviews, I think, of all the data flows. Like, you can do audits and things like that, but you have to stay on top, on top of it.

38:55Izar Tarandach Okay, so you just made my budget for privacy and security 4 times as big as it was before. Here at The Security Table, we are very big on things being reasonable. What's a measure of privacy for a company to decide what's reasonable for them to stand by their privacy goals? In other words, do everybody have to have the same goals? Or if I'm a very small company, startup, mom-and-pop shop, do I have to have the same thing as the big corporations?

39:32Ally O'Leary Uh, so there's a lot of factors that play into that. One would be, I would say, volume of data. I would also say the jurisdictions in which you have, like, you, do you just have US consumers? Are you small enough that you only work in Massachusetts, for example? Do you have global data? Those would be factors. And then the type of data, right? You could have, uh, there's, there's personal information and then there's sensitive personal information, right? So your name, email address, just standard personal information. But then there is sensitive data like bio, biometric genetic data. Um, Social Security numbers, things like that, trade union membership, they're actual data elements that are more sensitive. Medical data. So if you are processing that data, definitely you need to invest more in it because your risk level is too high. Also, if you are processing data of what's considered vulnerable populations, so children, elderly, things like that, you should also— you would have a bigger risk profile, and therefore I would think you would want to invest more in privacy and security. For those. So volume of data, type of data, like individuals which are collecting type of data, and your jurisdiction, I think.

40:39Matt Coles Okay, why does—

40:40Izar Tarandach what is the trade union— before we go there, sorry. No, actually, Matt, you go for it.

40:45Matt Coles So what is trade union data? Why is that private?

40:50Ally O'Leary It's, it's a sensitive topic in Europe. I will say, I, I will speak out of turn if I— I don't actually know the answer off the top of my head. It's very simple. Political affiliations, religious affiliation, all of that is also— I, it probably comes down to pro— profiling and then also making sure you're not making automated decision-making on a lot of those things. This is a bad example, but making sure you're not hiring an employee because— or not hiring an employee because of a certain religion they have, things like that. It's, it's— there's a lot that kind of goes into those factors that I could give you more information after.

41:19Izar Tarandach So that was awesome because that leads me to my next question, the how-to question. The more we talk about this, the more it sounds to me like that person that came to me at lunch and said, now I'm a privacy engineer. Was set up to fail, because it sounds to me that what you need is actually a lawyer, because there is so much interpretation here. There's so much nuance. Who, who are the people who are doing privacy, and who are the people who should be doing privacy?

41:49Ally O'Leary Yeah, that's a valid question. It's, um, it's a hodgepodge. I— what I would say is I think it's probably a 50-50 split right now of folks like myself who came from security and went into privacy because these laws popped up and there were no bodies. Or, or they were fascinated by it, or attorneys. It's a mixture. And so if you, you likely have a privacy compliance function that is led by an attorney— I am not an attorney— but, um, and, or you, like myself, work directly with privacy and security-related attorneys who help you interpret the law and, and come up with these justifications, arguments for regulators, help you balance the risk. So it doesn't have to be a lawyer. It's good it's a lawyer, but sometimes you don't want the lawyer because you want the person to be able to talk with Here's my other thing. I'm not a big fan of coming and being within the legal department because when you join a call, there's people know you're from legal, people just shut down. They don't want to say things, they don't want to talk to you. It's not—

42:47Chris Romeo yeah, guilty.

42:48Ally O'Leary And so I— here's what I like to tell people, and I like talking to lawyers.

42:51Matt Coles I don't know what you guys are talking about.

42:53Ally O'Leary I like to say, like, I'm not a lawyer, guys, please talk to me. And my argument, one of my big thoughts here is in any compliance role or a role where you have to give security requirements or requirements that people don't want to do, One of my big things is to actually build relationships with people. Like, literally let them know you have a job outside of this. You're not a, I mean, a family friend outside of this. You're not a police officer. Like, I like to, um, like, you can do things. It's just there's a certain confine of what you can do. And like, even I know people aren't in the office anymore, but I would like to like to strike up a conversation with a person in the hallway or like send them a funny meme over Teams because then they, like, you build a relationship, you build trust, and they'll actually raise issues to you and talk to you about things and actually work through things, which is huge. And then when you have to ask them to do something that they don't want to do, they actually understand, oh, I know why I have to do this. It's actually not— she's actually trying to help us here, you know. Um, so I think that's the biggest part of the job. And I think if you're an attorney— I love attorneys, I work with them all day long— people just immediately kind of shut down. So I don't think the actual— be an attorney.

43:55Matt Coles I know we're running short on time, but I want to ask this really important question And just related to, I think, what is it— where Sarah was going with this, what can we as security professionals do to help? Like, how can we as security consultants, advisors, experts, pros, whatever, and/or the security champion communities that we work with, what can we do to help facilitate or enable privacy and to facilitate those conversations or whatever?

44:23Ally O'Leary Yes, thank you. I would say, learn the definition of personal information. Understand it. Understand if where you work, you guys have it in any of your systems. That would be key. It's similar, like when I talk to architects too, if you become aware of any project or initiative that is going to touch this or change the system in any way, just be like, hey team, you might want to check with your privacy folks about this. Similarly, when we, when we go through reviews, if we know someone's going to store data, we have pointers like you're going to store it in the system, go make sure it's secure, work with the security team. So it's more of just a point them in the right direction because I, and I think my any colleagues in privacy would say we'd rather be notified than not. So, and then we will, we will work with them as needed. Yeah, I would say that. And also if you're aware, the other thing I struggle with is getting in the right spot of the development lifecycle. So if you are aware of certain gates or things like that where it makes sense to bring in a privacy person, we'd more than happy to participate. So, it's likely you guys, because security's been around for so long, it's likely you guys are already in the right conversations with the right people at the right point. They may just want to bring a friend in to listen and learn from there.

45:31Matt Coles So, obviously, we do a lot with threat modeling here. So, I mean, is that a good point where we should bring in privacy? If, you know, we find a data flow that has personal information on it, is that something we should do?

45:43Ally O'Leary Absolutely, yes. If anything more to like, did you guys even know this exists? Because I can't tell you how many times I learned about a business function doing something that we didn't know about.

45:50Izar Tarandach Out.

45:50Ally O'Leary So, and, and like I said, we were talking earlier about data flows, everything being manual, and there's no one system. So any triggers of a pocket where you might be doing something with data, definitely let them know and make sure it's on their radar.

46:02Chris Romeo Yeah, that's, that's excellent. Allie, thank you for, uh, walking us through this conversation. And, you know, the fact that you're thinking about developer empathy from a privacy perspective, this is something we've been thinking about for the last number of years as well. And, and it's just a powerful way to to connect with the people we're trying to influence. And so I love to hear that's kind of your perspective coming from the privacy side. And so, yeah, thanks for being our first ever guest around the Security Table. And just a quick message for those out there that might be ISO fans and might want to send me some, some, some select comments. You can send that to [email protected]. Wait, wait, wait, wait.

46:43Izar Tarandach There's a standard for that. Chat. It's iso.666.

46:45Chris Romeo Yeah, yeah, you have to look in ISO standard 17472747238-47, which will tell you how— I'm totally kidding. We don't send an email there because, because it won't actually go anywhere. So, but yeah, I mean, this is, this is, this is all in fun. Like, we around the security table, we do, we do argue about stuff. That's for fun. It's, it's to help us explore the ideas. And so, Ali, thanks for being with us as our first ever guest. And folks, we look forward to seeing you again soon around Security Table.

Transcript supplied by AssemblyAI. It may contain transcription errors.

View the original transcript on Buzzsprout

Originally published as The Security Table. Part of the AI Security Table archive.