6 ms·
Calling them the 'paranoids' probably seemed like a fun idea at the time, but I wonder if it set up a subconscious bias against their work. I wonder if they had
by Angostura 10y ago
Calling them the 'paranoids' probably seemed like a fun idea at the time, but I wonder if it set up a subconscious bias against their work. I wonder if they had been called 'The Guardians' or 'The Defenders' there would have been a different outcome.
Seems trivial, but words matter.
- sidcool 10y agoAs a developer who is not very much into security, I am guilty of this crime. Infosec teams are very important and deserve respect and attention.
- martin-adams 10y agoI used to slip in words like 'awesome', 'clever' and 'amazing' when talking to colleagues from other teams about the work that I was doing in the hope that it would influence their perception of the work. I've no idea if it worked though.
- dsacco 10y agoThe Yahoo Paranoids chose their own name. It was designed to be light-hearted in a way that didn't make them seem stuffy so that engineering teams would be more receptive to their work. In my experience, this is incredibly important from the outset. Anyone who has worked in information security for a month knows that the relationship between product engineering and security engineering defaults to antagonistic. It takes a lot of work to make it friendly and productive, and as a security professional I think "Paranoids" is much better for overall collaboration than something like "Defenders", which in my opinion reeks of self-importance. The more pertinent issue here is management not fostering the culture enough.
- Twirrim 10y agoWhere I'm working now, we've got security engineers assigned to seating in each development team. They're not managed by, or working for, our teams. They have their own manager and security work that they're getting on with. Having them sitting amongst the team, however, is resulting in a much different narrative than any I've been around before. There's a much higher quality, and less antagonistic kind of engagement going on. They've become someone you chat with at the watercooler, or at their desks, instead of having to file tickets, or wait for scheduled reviews to raise things. People can quickly consult with them and deal with a whole heap of small potential risks way early on in the development process, and it's paying serious dividends down the road.
- bananarepdev 10y agoThat approach Works well with Q&A too.
- wolf550e 10y agoSecurity engineers are seen as experts you consult about something you don't know. QA are not seen this way. Some QA engineers actually are experts that can give good advice on structuring an application in a more testable way, but that's not the norm.
- tracker1 10y agoMost QA guys only check that something meets the spec/story requirements, not that the code is sane or testable... many don't even go beyond UI testing. That said, I think GP was referring to having a QA embedded as part of a team.
- andersonmvd 10y agoYou're talking about Squads basically. Bring different people in the same group. And yeah, QA is very similar to Security in some points, but if you think straight QA should include security. Weird to say that a software has quality without security included, but the truth is that security is specific that the regular QA usually can't handle.
- rexpop 10y agoYou've capitalized Squad, but it's hard to Google. Where did you get that term, and where is it defined outside your head?
- xxr 10y agoNot the commenter you're replying to, but at least at my organization we borrow the term from Spotify.
- bananarepdev 10y ago
- dhimes 10y agoIndeed, regulatory and security are the two parts of the company that are supposed to be antagonistic in order to keep the company out of trouble. How that plays out in practice has a lot to do with the personalities involved.
- rz2k 10y agoI understand what you are saying, but having been around similar dynamics in the past I think such deprecation is a little like starting off the relationship apologizing for what they're supposed to be doing.
- bduerst 10y agoThat was my first thought when I read it. A better name would have been "Tron", "Patronus", or "Endor". Calling it "Paranoids" or "Inquisition" is just giving it another reason for people to loathe it.
- mhurron 10y agoInfosec isn't the ones doing the defending or guarding or any of that. They're typically working with the teams to do build and maintain to ensure their policies and procedures lead to and maintain a secure posture.