How are you dealing with the continued prevalence of ransomware attacks?
SVP in Finance (non-banking), 1,001 - 5,000 employees
You have to build resiliency. That's the conversation: you have to make sure there's a resiliency plan in place as you're designing new architectures, or deploying new technologies. Oftentimes the ransom has to be paid just to ensure the attackers do not disclose data. If they’re recoverable, the company can recover from their backups and be fully operational. But even if there is no major impact in terms of operations, the business still has to pay the ransom because of the potential consequences of a data leak. Network & Security Section Head in Telecommunication, 1,001 - 5,000 employees
We started implementing Zero Trust approach.Chief Information Officer in Manufacturing, 10,001+ employees
We have a Strategy in place to implement Zero Trust and are partnering with multiple 3rd party partners to support our Strategic Security Program. Content you might like
Yes65%
No, but I expect that may change.27%
No, and I don’t expect that to change.7%
Other (please specify)0%
322 PARTICIPANTS
CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.Data breaches due to remote work19%
Ransomware attacks43%
Lack of a corporate security plan21%
Missing security patches8%
Failure to inform employees of threats3%
Other (please specify)3%
350 PARTICIPANTS
Director Global Network / Security Architecture and Automation in Finance (non-banking), 10,001+ employees
Nothing ever dies in Enterprise. Why did Broadcom Software buy Symantec and VMWare, why did SDX Central post a story today about MPLS and how it lives on. Why is the hot news about cloud repatriation becuase a terrible app ...read moreHead of Information Security in Services (non-Government), 1,001 - 5,000 employees
You need to tell people what to expect and what not to expect from IT. We’ve tried to train people to expect that IT will do certain things or make requests which are okay to comply with, but IT will never call you out of ...read more
I saw this incredible write up from one of the Log4j maintainers on what it's like to be someone who's been volunteering their time to support code that powers half the internet, and then get yelled at all at once by everyone on the internet. It sucks when you think it through, of course. That's terrible. But for some reason, we're not planning ahead for that type of thing. And assuming that there will be swings and roundabouts that are uncomfortable for us to deal with, we need to try to ring-fence however we can.
I've been part of an open source group maintaining software before, and I don't think I ever thought about what the impact would be if somebody found a vulnerability in the code I produced. I can't imagine the vitriol the Log4j maintainers must have faced from all corners. It has to be hard for them as people who thought they were just doing good for the community.