Jeevan SinghGuest
Seth LawHostKen JohnsonHostDevelopers are, I mean, not only are they asked to ship more and more and more, but we talked about this ahead of time where they might be constrained as well on things like token usage.
If you're going to be called on the carpet and you have to remediate something, that something better be worth calling people on the carpet and making them do things.
How do you do a good job of getting high quality, highly synthesized and correctly prioritized vulnerabilities i feel like that's a huge critical part part of this yeah

yeah there's a bunch of critical parts so also the ownership model um making sure that we are a high response security team as well so um yeah we've always done a pretty good job like i my goal has always been two to three percent false positives at most because you want to have the trust of the engineering team um so and i'm not saying we get it right all the time um we do definitely get it wrong and we we solicit feedback from engineering we we prefer when they provide us feedback and say i disagree um we have a much better conversation when it comes to with respect to that um so yeah it is i love that yeah they do trust us um we are not We don't want to be heavy handed.

At the end of the day, engineering is also driving the business and generating a lot of profit for the, or a lot of revenues for the company.

But like, we also want to make sure that they are aware that there are consequences as well.

If something goes wrong, it's easy for us to quickly change the team and make sure that the right team is jailed instead of the wrong team.

Fortunately for us, we have a large sizable team in India, but also a large sizable team in North America as well.

So if someone's asking or saying, hey, there's something wrong with this, we need you to We'll look at it.
Developers are, I mean, not only are they asked to ship more and more and more, but we talked about this ahead of time where they might be constrained as well on things like token usage.
If you're going to be called on the carpet and you have to remediate something, that something better be worth calling people on the carpet and making them do things.
How do you do a good job of getting high quality, highly synthesized and correctly prioritized vulnerabilities i feel like that's a huge critical part part of this yeah

yeah there's a bunch of critical parts so also the ownership model um making sure that we are a high response security team as well so um yeah we've always done a pretty good job like i my goal has always been two to three percent false positives at most because you want to have the trust of the engineering team um so and i'm not saying we get it right all the time um we do definitely get it wrong and we we solicit feedback from engineering we we prefer when they provide us feedback and say i disagree um we have a much better conversation when it comes to with respect to that um so yeah it is i love that yeah they do trust us um we are not We don't want to be heavy handed.

At the end of the day, engineering is also driving the business and generating a lot of profit for the, or a lot of revenues for the company.

But like, we also want to make sure that they are aware that there are consequences as well.

If something goes wrong, it's easy for us to quickly change the team and make sure that the right team is jailed instead of the wrong team.

Fortunately for us, we have a large sizable team in India, but also a large sizable team in North America as well.

So if someone's asking or saying, hey, there's something wrong with this, we need you to We'll look at it.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.