A Better Way to Pentest for Compliance
Compliance testing and security testing often run as separate efforts. Eastman Chemical's CISO and Synack's co-founder explain how to meet regulatory requirements and reduce real risk with one pentesting program. Large organizations juggle regulations across countries, multiple cloud providers and a growing number of suppliers,…
Adam Keown CISO, Eastman Chemical
David Hale Partner, Brownstein Hyatt Farber Schreck (moderator)
Overview
Compliance testing and security testing often run as separate efforts. Eastman Chemical’s CISO and Synack’s co-founder explain how to meet regulatory requirements and reduce real risk with one pentesting program.
Large organizations juggle regulations across countries, multiple cloud providers and a growing number of suppliers, while the experts who can test well are hard to hire. Too often, pentesting for compliance becomes a point-in-time exercise that satisfies an auditor but says little about risk the day after.
In this session, moderated by privacy and data security attorney David Hale, Adam Keown, CISO of Eastman Chemical, and Jay Kaplan, co-founder of Synack, discuss how regulation was raising expectations for security testing, how Eastman assesses supply chain risk, and how to prioritize assets so that compliance and risk reduction come from the same program.
They also make the case for continuous testing alongside scheduled assessments, and for a holistic scope that covers web and mobile apps, APIs, cloud and on-premises infrastructure and endpoints.
Recorded in 2022. Titles and the regulatory developments discussed reflect that time.
What you'll learn
How regulation is raising the bar for testing
Why regulators increasingly expect organizations to show their controls are in place and tested, and how supply chain obligations extend testing to vendors and contractors.
How to align compliance with real risk
Map the attack surface, prioritize the riskiest assets, then scope compliance testing for systems holding sensitive data, and treat noncompliance as a business risk in itself.
Why point-in-time testing falls short
Adam Keown's case for continuous testing, and why a holistic scope across apps, APIs, cloud and endpoints matters when everything is interconnected.
Chapters
Jump straight to the part you need.
Full transcript
Read transcript
Hello and welcome to A Better Way to pentest for Compliance, a Synack webinar. Please feel free to ask questions at any point throughout the presentation. There will be experts behind the scenes to provide answers. If you want to speak with someone from Synack directly, you can reach us through our website or by requesting a meeting or demo through the navigation bar at the bottom of your screen. And lastly, if you'd like to revisit the content presented, you can use your email and unique URL to access the webinar on-demand. Thank you again for joining us, and now I'll turn it over to David Hale, our moderator.
Hi. Welcome to the webinar. Thank you for joining us. My name is David Hale. I’m a partner at the law firm Brownstein Hyatt Farber Schreck. I focus my practice mainly in the area of privacy and data security issues. Joining me today is Adam Keown, who is the CISO from Eastman Chemical, and Jay Kaplan, who is the CEO and co-founder of Synack. I know Jay is going to talk about Synack a little bit
later, but Adam, can you maybe start by giving us a little bit of background on Eastman Chemical and what your role is there? Sure, David. I'm happy to expound a little bit. Eastman is actually a Fortune 500 specialty materials company. We actually started a transition back in 2012, moving from a diversified chemical company to a specialty materials company.
And today we manufacture and market advanced materials and specialty additives. We've got four main business segments, which are advanced materials, additives and functional products, chemical intermediates and fibers. And we also employ about 14,000 employees globally. And just for for fellow IT folks out there that that ramps up to about 20,000 user accounts globally with all the contractors and other folks,
and we’re thankful to be able to serve, as you see, in over 100 countries. Eastman as a whole. Next slide please. Eastman as a whole, as I mentioned, has a broad global presence. We've got almost 40 manufacturing locations, including joint ventures in 13 countries worldwide, with the majority of our revenue, as you can see, coming from outside of the United States. We also have research and development and technology
centers located around the globe, which enables us to replicate customer processes and to serve better all the customers and collaborate more effectively. But that's the quick glimpse of what Eastman looks like. Thank you. You've got a big job. Well, we're here to talk about compliance and security, security points and pentesting. So let's let's start off, you know, right off the bat with the first question. What what, from your perspective,
are the biggest obstacles that you face and that that security leaders face when when they're dealing with pentesting and compliance questions? Yeah. The... I can tell you not only Eastman, but even in my previous roles, the the difficulty around finding talent is always a rough issue. I believe that pentesting is, I don't know, 70, 80% automated tools, stuff that almost anyone could run.
But then there's about 20 to 30% of pentesting and even meeting compliance needs. That's almost an art. It takes someone who's an expert in that field to be able to make a server come alive or come to its knees is maybe a better description, or to have an application, you know, spill the beans about the data that's behind it. And
so where I see difficult areas is not only keeping up with compliance and regulatory matters, but also having the right talent in place to be able to touch the art side of pentesting. If I could just add to what Adam said, and thanks David for moderating the panel, Adam for being here. You know, I think what we heard from customers early on when we
started the company back in 2013 was that it was very clear that our customers were either thinking about pentesting or thinking about compliance in two separate ways. They were not able to achieve the same thing by conducting one assessment. pentesting was looked at as a good security practice to understand when an adversary was trying to compromise an environment, what are the vulnerabilities
would they take advantage of, and from a compliance perspective, they were simply looking to check a box, and so I think the reality is that they need to be doing both, and so what we thought at Synack was, is there a way to be conducting a test that also enables a customer to achieve, their compliance requirements from a security diligence perspective, particularly on the vulnerability side.
I think there’s the old saying: compliance does not equal security, and that may be true, but let's face it, compliance is still an important part of your security program and your journey, and I'm sure that's certainly the case for Adam, as he's faced with juggling a lot of different requirements today. Yeah. And I think, you know, that's going to, only become... Compliance is is... Well, we need to distinguish between the difference between
compliance and security, functional security. Compliance is an important aspect, right, and it shouldn't be ignored, it's only going to become more important, you know, over this next decade as regulations, worldwide, but especially in the United States, start to emphasize the idea of being able to demonstrate that you have security controls of various sorts deployed and that you're testing those controls.
So where, health care and financial services have had regulations in this area for, almost two decades, there's a whole series of laws that are coming proposed or, you know, in the works that are bringing those same types of security realities to other sectors in the economy. There's most particularly in the critical infrastructure realm, which Eastman is a part of,
there's a recent executive order, which is one of a series of executive orders over the last ten years by three different presidents. But the most recent one requires for critical infrastructure and for companies that are doing business with the U. S. Government that they be able to demonstrate that they are actually testing their products, testing their processes to make sure that they're that they don't have vulnerabilities, that they would that would expose them to critical issues.
In addition to the to that executive order, you've got things like proposed SEC rulemaking, Securities and Exchange Commission for publicly traded companies, which is going to require, you know, first disclosures of data breaches, but maybe more apropos to this conversation, also will require a disclosure, for publicly traded companies about about how they approach securing their infrastructure.
What do they do in terms of, in particular, testing, but also, remediation of the results of that testing. How do they learn from things that they've, from mistakes that they've made in the past, etcetera. That proposed rulemaking was made back in, I think it was March of this year. Comments were due in June, and the SEC is ingesting that, and we should hear something from them, I think, soon. The FTC likewise has has just opened up a set of of
proposed rulemaking. They've they've, asked for people to give general comments there, but the the outlines of what they're looking for comments on indicate that they are also going to be looking at security with a much more skeptical eye than they have in the past, you know, twenty years, and being more aggressive about the idea that failing to have security and failing to test the security that you have is somehow an unfair trade practice.
Right? So it somehow damages people generally to have that, and that therefore, you know, you might be liable. And then finally, there's proposed federal legislation, which this summer was looking like it might be very, very close to passing, then maybe not so much. But in the last in the last day or two at the end of September, the... That's changed again, and it looks like maybe this might actually come to a vote
before the end of of this legislative session. If that legislation passes, that's gonna require companies certify that they have security processes in place, that they have privacy processes in place, and that they're testing those processes, which will, you know, of course, lead to a huge need to be able to identify potential vulnerabilities and take action ultimately on those vulnerabilities.
And, of course, as part of the certification process, we'll require documentation of all of that. So the issues that have been around for years in some industries are definitely going to become much more widespread across industries, and companies that start to take those to start to make efforts to bring themselves into compliance with where that's going are going to be ahead of the game because the compliance deadlines on these are going to
be probably shorter than most companies are comfortable with in terms of suddenly coming into compliance. So with that, I mean, one of the main issues that will be an issue in all of those regulations is dealing with your supply chain. What do you guys do in terms of reducing risk relating to supply chain? David, that's a great question.
When we're looking at our supply chain and not only where we're getting raw materials and, we're also concerned about, where we're getting IT equipment from, what vulnerabilities are in that IT equipment. And so we conduct assessments through various methods on these companies. We also look at what their financial records are, what their
history is. We consider all of these factors and risks around what’s leading into that supply chain. Even more recently, we've taken steps to look and see what code. There's a lot of talk in the industry around software bills of materials, SBOMs, and we’ve taken steps to look to see what code is even included in specific applications that are delivered to us. I can even tell you a recent story that,
we hired a big contracting firm to build an application for us and they said the code was secure. It was ready to go and after delivering it to us, we ran it through just a standard code scanning tool that we have here on-prem, and unfortunately it came back with lots of either vulnerabilities or or they were using old software packages in the code that they provided us. So we’re having to take a multi— My point is,
we’re having to take a multi-tiered approach to understanding the type of supplies that are coming into the company, not only on the physical side, but especially on the digital side in order to make sure that we stay protected moving forward. I think Adam brings up some really great points and you know one of the things that we're certainly seeing at Synack from our customers is this realization that they can't be siloed into just looking at their own infrastructure or their own homegrown
assets, web apps, etcetera. They need to also be looking at those assets that are, that their technology infrastructure is interfacing with on the contractor side. So, you know, software, extends beyond just an enterprise's perimeter extends to contractors, subcontractors, and they're now a lot of our customers are now saying, all right, well, it seems like it's really hard to even trust that they're
doing the diligence necessary to make us feel comfortable, when they're housing our data. We need to start assessing their technology to make sure we feel good about their vulnerability posture, and so we're now extending the Synack product into their their contractors and subcontractors' security programs, which is which is really an interesting evolution. Yeah. And I would add that a sort of optimistic
spin on that is that as opposed to, say, ten or fifteen years ago when, if you were trying to do that kind of testing of your, suppliers or trying to negotiate, commitments to security standards from your suppliers, you would be sort of met with a blank wall, right, or a blank stare. Today, mainly because of regulations in Europe and the United Kingdom, that's evolved, right,
and it's a little bit easier to get folks to understand that, yes, they need to make these kinds of commitments and that people have an obligation to make sure that their vendors are handling information appropriately on their behalf. And so while it’s a challenge in terms of getting that check actually done from the perspective of either scanning or or other analysis of of the vendor,
you at least are able to get past that initial question of that assertion of, well, I need to be in your... Inside your walls. I need to be in your business. I need to understand how you are doing this because I can't just take your word for it. But that actually highlights a question that I think is important for us to look at. There's this question of compliance on the one hand and risk addressing actual risk on the other.
How from your guys' perspective, how do you prioritize those two things at the same time? You know, are they are they... To what extent are they opposed to each other or dissimilar from each other? And how how do they really align in your experience? Maybe we'll start with Jay this time since we started with Adam last time. Yeah, sure. It’s a really great question, David. You know, I think our customers are certainly turning to us to try to figure out
which of their assets are the riskiest that they should prioritize from a pentesting perspective, because at the end of the day, you can't do everything on every asset in your environment. It’s just cost prohibitive to do. We certainly would love them to do that, but at the end of the day, it's particularly from a continuous security perspective, it's really hard to perform a comprehensive continuous security assessment on every asset across your global network and
application footprint. And so by trying to basically first map out that attack surface, understand what are the things that you have and then going a step further and saying, okay, of these assets, which are the riskiest that we need to be assessing from a pentesting perspective? I think that's step one. Then step two is, okay, now which of these assets do we actually need to test from a compliance and regulatory perspective? Which of these assets is housing sensitive customer information, PII, credit card information,
healthcare information, etc. Obviously, you have to look at those a little bit differently, but I think it is all part of one holistic program, and ultimately, it needs to really come together and the right cadence needs to be deployed across those assets once you are properly able to prioritize the risk profile. I'd be really curious to hear Adam's take on this. I mean, you have so many assets in your environment to look after on a regular basis. How do you know which ones you should be assessing regularly
and how much of the how do you know which ones you should be looking at from more of a compliance and regulatory standpoint? Yeah, that's a great lead in Jay. Even with 600 IT employees here at Eastman, we can't do it all. It's just impossible. One thing I try to keep in mind is that compliance needs can also provide risk metrics for us.
At the same time, being noncompliant is a risk in itself. So you're looking at financial risk, you're looking at reputational risk and other items by being noncompliant. So we have to play this balance game on a daily basis and we can't ignore it. Being a global company, we have many areas and other governments, not just the United States that we have to consider with the
compliance needs that we put in place. And it's difficult to keep up with all of those. And so we not only take a risk approach at vulnerabilities, take a risk approach at compliance constraints that are out there or controls. We then take a look to see how can we apply these in both areas. There's such a there's such a discussion in the past about a
point-in-time and that's what to me. That's what compliance always tells me. You know, when the auditor came in at that point-in-time, were you compliant? And the answer is yes. When risk is more of a is a is a movement over time. It’s a more holistic picture of what’s going on. You know we can we can run a scan once a month on the thirteenth or the day before or after Patch Tuesday and get a different compliance answer.
But risk is about how long were we exposed and how much time did we have out there that we weren't patched or that we weren't meeting a specific control that a compliance or regulatory body had in place. So we, you know, it's they're both they're both needed in order to operate successfully in this world and we have to play the advantages off of each one. So, you mentioned that you have 600 folks,
and even with that, number, you've got a problem in terms of balancing all of the demands that are required. Recent studies have shown that 90% of CSOs consider themselves under moderate or high level of stress. How do you manage that? How do you reduce burnout and stress for yourself and your team? I well, I can tell you right off the bat, I don't have a magic pill or a magic answer to that,
but I can tell you what I do personally. I don't you know you hear lots of folks talk about a balanced life and I believe that there are aspects that we can take on that are are time-sensitive, or that we focus in certain areas at certain times of our lives. You've got when it comes to things like children and such, you've got certain parts of your life that
they take more time than they don't. Those type of same scenarios happens in the IT world. You know there's certain threats that are out there that we have to spend more time on than others. There are specific vulnerabilities or specific software packages that we're having issues with. So what I do is I try to take them one at a time as they come and focus realizing that I can't get to everything all the time and make it all happen.
And so not only having a personal life that is away from the IT work and away from some of the security items, but also in my day to day job, understanding that I have focus areas and priorities every day. And if I'll just attend to the priorities, then everything else will take care of itself when it gets taken care of. Yeah. Jay, any thoughts? Yeah, no, for sure.
I mean you know look we hear it all the time. Not only can our customers not hire the talent that they need, the talent they have are stretched incredibly thin. The reality is, it's incredibly hard to balance everything, and it's one of the reasons why we created the Synack Platform. It was really to give our customers an opportunity to augment the resources that they have and leverage talent in more of an on-demand fashion when they need it.
We instituted a credits model at Synack about a year and a half ago that gives our customers a lot of flexibility, so they basically can purchase a predetermined number of credits at the beginning of their contract, and as requirements come up, whether they're security testing requirements, compliance requirements, etcetera, they can start to leverage our talent in a variety of different ways and draw down on those credits, really augmenting those teams. What I've talked to a lot of our customers about strategically is figuring out, okay,
what is the core competency of your team and what are the areas that you can take away some of the stuff that maybe they shouldn't be focusing on a regular basis. Obviously, there are a lot of advantages to using an external firm for testing purposes, because they're taking more of that adversarial approach. They don't see the environment every single day, and they're probably looking at it very different than internal resources are. But I think at the same time,
having almost unlimited scale where we are leveraging freelancers in 90 countries around the world, it enables our customers to not have to be burdened and choose. It enables them to do all the things that they want to do, but simply select, okay, I think these are things we need to do internally. We have capacity to do these specific things from a strategic remediation perspective as just examples, and let's offset the rest of it to third parties,
like a Synack and other services. So, it's really exciting to be addressing this problem of burnout, you know, with our product, in a really unique way. I think this is something that hasn't been possible in the past. And Jay, I'll jump back in on that here, for just a moment. That was something that we took advantage of at Synack. It was just, you know, and you know there's other folks out there that offer different types of areas you can think of not just pen testing but, SOC.
Like some people outsource their SOC. It's not something we do here at Eastman, but it is something other folks do. But it helps. It helps my team focus on those areas that I was discussing earlier that are the main things that they can only do because they do know our environment and we can let some of the we can let some of those other items be handled by third party folks. It works great. Speaking of using third parties,
one of the big transformations in the last ten years in addition to regulatory is moving to things like cloud, you know, moving to containerized solutions, etcetera. How has that evolved how you work in terms of using, you know, pentesting or other security tools to secure your systems as you engage in this digital transformation and start to adopt the new
technologies that are well, not so new anymore, but the radically different challenges that are posed by things like cloud and securing your API framework. Yeah, when it comes to Eastman, So we use multiple clouds. We use multiple types of containers. We use multiple, I think anything you can think of. We've got a version of it somewhere that we're using.
The difficulty is keeping up with all the changes that happen in those environments all the time. You know, whether whether you're whether you're using one of the big three cloud environments or even one of the smaller ones, they're all updating. They're all saying, hey, we've got a new area. We've got a new API even for certain security logs. We've got a new API for understanding what developers are doing, whether it's foundationally
encrypted or not, there we can't even keep up with all the changes that are being made and are available. So that's one of the reasons why we can we can use things like pentesting efforts and such in order to shore that up to make sure we're meeting those compliance needs. Keep in mind areas in compliance also change too. The governments are passing either new compliance laws that may not keep us in compliance.
That's just a hard thing to keep your arms around. It's like trying to wrestle a gorilla or wrestle a gorilla running down a road. It's just trying to keep up with those items is tough. And it especially occurs with APIs. You know, we're developing software in house. We’re buying software externally, bringing all these things together and ensuring that they're secure is a big game. And we have to we can't rely on just the team that we have. We have to use third parties to make that happen.
Sure. Jay, I'm sure you guys are leading the way in terms of dealing with questions like, you know, API discovery. What do you guys what are you guys doing? Yeah. I mean, hit the nail on the head, right? I think, you know, one of the key genesis behind starting Synack in the first place was to figure out how to better align to the changes that are ongoing in any enterprise environment. That could be on the application side,
developers consistently pushing out code changes and practicing agile development that have more of a DevOps culture, or it could be on the infrastructure side as they're pushing to the cloud, changes in those cloud environments, zero-day vulnerabilities, etc. How do you stay on top of all this stuff? Because I think the reality is pentesting historically has been a very point-in-time driven solution, and it's been very focused on just that peak time period that
you're doing the test. But as soon as something is updated, that full pentest is invalidated. And so when we started Synack, we had a continuous only product that has certainly evolved over the years, but the goal here is how do we stay on top of changes and reassess those changes in a highly dynamic manner and help our customers reassess for potential vulnerability. You know, we fit incredibly well into companies that are going through digital transformation, those that are trying to fit
pentesting into their DevOps culture, and it's been really exciting to see that transformation, you know, in just their pen testing programs. That's a great segue. What new technologies, solutions are you guys using in from a pentest perspective on your teams? I guess maybe maybe Adam, you can talk a little bit about from from what you're using and Jay, what you're, you know, what you're developing.
Yeah, Jay's last comment is I was ready to hop on my soapbox there. I'm tired of these point-in-time wins in a compliance sense. You could have everything buttoned up and perfect one day and the auditors come through and they test everything and the next day it's in shambles for not only the environment changing, but that your team can't keep up with it. Maintenance and other items. I have been a strong advocate
for continuous monitoring, continuous performance evaluation, continuous pentesting. This point-in-time stuff is is a decade ago or longer. All companies have to move into continuous monitoring. I briefly discussed it earlier looking at the overall risk, in not just a point-in-time if you tested it the day before or after Patch Tuesday. You've got to.
All companies have got to move into continuous activity for all their measurements. Otherwise you're not going to be able to keep up the attackers out there, the advanced persistent threats, all these other folks, they're not waiting to come at you the day after your compliance checkoff happens. Just isn't the case. Jay, I'm sure you'd like to jump in on my soapbox with me. Go ahead. No, I mean I think you reiterated I think a lot of
what I said and I think we are very aligned in how we're thinking about the world. You know, I think the one thing I'll add is just that when you're when you're thinking about pentesting, it can't be in a bubble either. Like, you you know, I see time and time again customers that tend to just focus on their most critical applications, from a pentesting standpoint, and they totally forget about the rest of the environment, and if you don't take a holistic approach to looking at
everything, you're going to leave the door wide open, because everything is interconnected. Everything is being shared through APIs, common networks, common frameworks, etcetera. There are always there's always a path. You can jump from an application inside an internal network to a domain controller and compromise the integrity of a whole network. Like, that is very, very possible. We see it time and time again, and so, you know, I think as customers are looking at assessing their
technology footprint, they have to be thinking about those web apps, those mobile apps, the underlying APIs, even headless APIs that may not have an interface sitting on top of them, all the cloud infrastructure, all the on-prem infrastructure and the endpoint devices. Devices. There needs to be a comprehensive and holistic strategy as you're thinking about vulnerabilities. Yeah, in one of my pentesting teams, one of my roles in the past, the pentesting team I was with, we compromised Active Directory from a scan
gun inside the warehouse. You've got to look at the full digital landscape here. You can’t just focus on these individual items or the main ones that that the company likes to focus on. That's actually awesome. I would love to learn how they did that. That's amazing. It's even better. I mean, everybody's favorite punching bag is, you know, the target breach, right, which originated with an HVAC vendor.
But that may be even better, the scan gun. It was. Jay, you want to give us a little bit of information on what Synack is doing now in terms of how you've built your pentest for compliance product? Yeah, absolutely. I think I alluded to this previously, but our credits construct has really given our customers tons
of flexibility and the ability to leverage Synack in a much more agile manner. So being able to sign one contract at the beginning of the year, not have to deal with multiple vendors, juggling resourcing requirements, figuring out when they can start something, and, you know, is there availability from a vendor perspective? It just gives customers just a better way of doing things from both a pentest and compliance perspective. So, you know, look, we have continuous testing,
that also gives you the ability to be compliant. I think that's an industry first, so being able to offer continuous manual pentesting with compliance baked in, I think that’s kind of the most amazing thing you could possibly imagine in this space, and it might not be for everyone, but for most companies that seems to be resonating really well. We also have consistent, very well written vulnerability reports that are super easy to
understand, both from a technical and nontechnical perspective. Whether you want an executive summary or you want that more technical report generated, you can generate those in real time in the platform. Everything is centralized in our platform. We are testing for a variety of different methodologies and PCI, HIPAA, NIST, you name it. We have created specific checklists for those frameworks to make sure, that we can give you the attestation that we’ve checked
everything necessary from an auditor standpoint. We also have built-in patch verification, which is very unique. It's one thing to be fixing an issue. It's another to make sure that there is not a regression or that you’ve actually fixed the issue you intended to fix. So being able to kind of round out that life cycle of remediation, I think, goes a long way. We have flexible pentest durations, really fast deployment where you're typically up and running in twenty four hours. Self-service is also built-in,
and I think one of the most unique things that we offer relative to any pentest in the industry, whether it's from a consulting shop or elsewhere, is we give you platform coverage analytics, so because all of our testers are conducting testing on our infrastructure or routing through our infrastructure, we see everything, and so that gives you both auditability and a sense of control, but it also does give you those analytics and that data, so you can have confidence that you're getting the coverage that you hope you're getting.
So, big picture here is to really help organizations along their journey from both compliance-based to risk-based pentesting. We feel like we've paved the way to enable our customers to not have to worry about pentesting anymore, to sign one contract and to be done with it, and getting all that diversity of researcher resources, 50 to 75 researchers deployed on a project at once, coupled with all the capabilities I just mentioned.
We're really excited to be super innovative in this space and really changing the game as it relates to pentesting, particularly pentesting for compliance. Thank you, everyone, for joining A Better Way to Pentest for Compliance. Thank you Jay. Thank you Adam. Thank you David. Please let us know, as David mentioned, if you have any questions over email or you can also use Twitter. Thank you again and have a great day. Bye bye.
No lines match that search.
Speakers
Adam Keown
Eastman Chemical
CISO
CEO and Co-founder of Synack
David Hale
Brownstein Hyatt Farber Schreck (moderator)
Partner
Frequently Asked Questions
Should pentesting for compliance and pentesting for security be separate?
Which regulations were driving more security testing?
How can organizations reduce supply chain risk?
How do you balance compliance requirements with real risk?
Why move from point-in-time to continuous testing?
What should a holistic pentest scope include?
How can security leaders manage stress and burnout?
Keep exploring
Keep exploring
A Better Way to Pentest for Compliance
39 min
Threat Exposure Analytics: Measuring and Communicating Security Risk
How to prove which exposures matter and report them to leadership.
Watch →Continuous Pentesting: From Discovery to Proof
From asset discovery to validated, exploitable findings in one platform.
Explore the demo →Free Sara AI Pentest
Run a pentest on an approved web app or up to 100 IPs.
Apply now →Watch next
63 min
Oct 15, 2026
Threat Exposure Analytics: Measuring and Communicating Security Risk
Most exposure reports count findings. Leadership needs to know which ones can reach the business, and whether risk is going up or down. Security teams collect…
Roselle Safran KeyCaliber
63 min watch
25 min
Nov 13, 2026
AI vs. Cybersecurity: What's Actually Changed?
AI is helping attackers find and exploit vulnerabilities faster and at greater scale. Deep penetration testing still matters, but periodic tests alone leave gaps as applications,…
59 min
Nov 2, 2026
Public-Private Collaboration Advances in U.S. Cybersecurity
A year after Executive Order 14028, leaders from CISA, Accenture Federal Services, the Vaillance Group and Synack assess whether public-private collaboration is working, and what it…
Dr. Allan Friedman CISA
59 min watch
Next step
Meet compliance requirements and reduce real risk with one program
See how teams use Synack to test continuously, validate exploitable risk and report results to auditors and leadership.


