Bitdefender found that 70% of cybersecurity professionals often have to work weekends to address security concerns at their organization
Over 70% of cybersecurity professionals often have to work weekends to address security concerns at their organization, according to a new report by Bitdefender.
This intense workload appears to correlate strongly with job dissatisfaction, with around two-thirds (64%) of the 1200 cyber professionals surveyed stating that they are planning on looking for a new job in the next 12 months.
The issue of burnout and job dissatisfaction was particularly profound among UK respondents, with 81% often working weekends and 71% looking for a new job.
i got that, the stress is not worth it. the previous generation didnt need to work 24/7 every week to earn what i did with all the commissions included.
get people to rotate out with me. i'd rather get less pay (provided its sufficient for living) than the chronic stress.
Change Windows. You can't take shit down during the work day.
Everywhere I've worked (many very large companies, banks, telecom, outsourced IT, etc) teams have coverage schedules, so I suspect this article is misleading.
Someone has to mind things 24/7, this is done via scheduling.
And the more critical you are, the more on-call you are. I had one role where I was on call 24/7. Things rarely broke enough for me to be called, but I never once resented when I was called. I'd rather get woken up at 2am because my help is needed than have the risk that our systems aren't ready for the day.
And the more critical you are, the more on-call you are.
This shows a really low Bus Factor which should be remedied. If you're on call 24/7 because you're the only person who can fix things then your employer is running the risk of you being unavailable due to injury or disease and then they're up shit creek sans paddle.
Not to mention that lots of malicious attacks occur late at night or on weekends in an attempt to delay getting noticed. My company has rotating on-call schedules for our security, devops, and even engineering teams. I’ve had to hop on late at night or on weekends to help mitigate attacks. Luckily my employer is really good about letting folks take a day or two off after such events.
High availability and security are the bane of IT infrastructure jobs. It makes me anxious to think about my MSP days when I'd sit on my couch on a Saturday fully aware that I'm one phone call away from having my day, weekend or even the next two weeks ruined because some customer CEO has full domain admin rights and would give them to anyone who'd ask on the phone or via email.
It's not just security that ruins an IT person's life. I had a customer decide to do a massive data migration from their primary data storage to a new system during the busiest time of day. It destroyed the primary, secondary, and backup systems as well as corrupting the destination system. It was a one-in-a-million bug/glitch that cost me 2 weeks of 16 hour days.
It's idiots in charge of IT that are the true source of our pain.
My org has a follow-the-sun rule and avoids having people work on weekends. It helps that it's a global team, so there's only around maybe 18-20 hours in the middle of the weekend where it's not a Monday or Friday somewhere in the world.
My company doesn't work weekends unless you're on call or something. I could see it happen with incident response or security operations, but other things aren't so critical that we need to have our staff working outside of normal business hours.
I may be lucky as well because I work within GRC, and we have a huge focus on work-life balance.
And ~100% of cybersecurity pros work ad hoc 100% of the time...
They probably put in 2-10 hours of actual work in a given week. Just like any desk job that doesn't sit on zoom calls all day.
Edit: 100% of people downvoting this should first Google "ad hoc." Or are just envious that I have a cybersec job making good money doing nothing all day. Sucks to suck. 🤷♂️
Kinda how ~100% of IT salaried positions work. If you're confused, you're probably hourly.
If you're paying someone to always be on call then they are always working. Just because you don't always need them doesn't mean they aren't working. You're paying for their availability.
Since we're telling people to Google things, try "anecdotal fallacy" and let us know if it helps you to understand the source of the downvotes.
The OP is about survey data that directly contradicts your position. It's fantastic that you've found a position where you have work/life balance that works so well for you, but it simply doesn't match the experience of many commenting in this thread or those who were surveyed.
Be as obstinate as you like, it won't change the lived experiences of others in the industry.
If your cybersecurity and/or SecOps team isn’t working 40 hrs a week, you’re either WAY over staffed or you’re missing out on a lot of proactive security work. Ours has a massive backlog of tickets and is working proactively on protecting and preventing incursions and security incidents.
No, SOAR tools make life pretty easy. 5 person SOC team + boss, 700 person org. Not overstaffed.
I get a few alerts every few hours. Investigate, determine if false positive, and go back to gaming. Unless it's the off chance it's not a false positive. Then I do an hour of work or so. Then back to gaming.
You are one of these people that also thinks the utility companies sit on their ass while they are not performing a break-fix aren't you?
If anything security means ploughing through logs, checking up on monitoring alerts. And most importantly constant lobbying with the devs and deployment projects to actually take security serious.. yes we know it is easier to deploy without ssl, single sign on, firewall, monitoring suite and not using our template but your own custom OS install etc.. but this means everything is fucked if something happens and noone will be able to tell why. And No you cannot just deploy the database cluster in the DMZ so that it is easier to access.
Oh boohoo, you make 6 figures and have to work some weekends. Get over yourselves or better yet, get a job outside of a cubicle. Every job is going to have it's good aspects and shitty aspects.
So would you rather work weekends, or up on a roof in the Florida sun?
You gotta understand the skill set is highly specialized and is ever-evolving. The issue likely being that many take on their six figure salary and aren't paid for their weekend work but instead work to ensure the security of the employer.
If I'm hired for $120k/yr for a 40hr week, but I'm pulling 46-52hr weeks, I would feel the need to be appropriately compensated for it. If it's going to be considered a work hazard I would expect to receive hazard pay.