r/ciso • • Aug 05 '25

Vegas - What a Dump

153 Upvotes

Warning: jet-lag induced travel whining...

Welcome to Black Hat. Hotel wireless reminds me of 2003. Facilities are outdated. You can't walk anywhere, it's pedestrian-unfriendly. A burger and fries costs $45, and after booking a hotel online, you get hit by another $175 'resort fee' package when you register?

Private IP doesn't work on the 'free' WiFi, and even if private IP is off (only slightly less ill-advised then using hotel wireless), the captive portal is unresponsive. Hotel 'tech support' told me they'd whitelist our device, requested I power off for 15 min, and connect back up (pretty sure her shift ended 10 min into that restart period). Of course, that didn't work.

Travel is down in Vegas, dramatically. Like... you can see the difference. There are no crowds. Uber arrives in minutes. Plenty of room on the airport tram. Hotel shoppes are empty. Kiosk employees look bored to death. Hotels are selling 2-for-1 show packages in an effort to fill seats... And this is their response? Make travel even more heinous, and jack up the fees?

Time for Blackhat to relocate.


r/ciso • • Sep 30 '25

Got hired with no experience as a CISO.

106 Upvotes

Just looking for some advice.

I recently accepted a position as a CISO for a local government agency. They just started this role about 2 years ago. In my area there are maybe 1 or 2 people with the actual title of CISO.

Well the position opened up and I applied for it. Honestly didn't think I would get it because my whole career in IT has been doing infrastructure work. I've handled Security Awareness Training programs, deal with our EDR and ITDR, but I rely on our MDR for the technical stuff (threat hunting, IR, etc). Well, they offered me the job (I believe I interview well).

I feel a lot of anxiety setting in with my last days at my current employer coming up if I made the right decision. Where I'm at you could basically call me the IT Infrastructure Manager. I'm coming from an extremely comfortable job where I make good money (I'm not leaving for a huge pay pump) and able to go home at night with little or no stress.

I've always wanted to get into the cybersecurity side of things, but this is jumping in face first. There's a lot unknown's of how this company handles things (I know for a fact they have no MDR, or at least a SIEM). I could be walking into something bad; but it's possible it's not as bad as I think.

Has anyone been in this boat before?


r/ciso • • Nov 13 '25

I don’t think many people understand the physical and mental toll a cyberattack can have on a CISO.

80 Upvotes

Tim Brown’s story on how he lost 25 pounds in 20 days and suffered a heart attack following the SolarWinds incident hit a nerve for a lot of people in security. And I think that’s because we know it’s not an isolated story - it really is the quiet reality behind so many big breaches.

CISOs and security teams are burning out, losing sleep and carrying the pressure of keeping tens of thousands people safe.

We spend so much time talking about incident response plans, detection systems and technical resilience, but human resilience needs to be talked about too. There’s no playbook for what happens after you’ve spent weeks in crisis mode, or how you come down from that level of intensity when everyone else has moved on.

It’s easy to say “it’s the CISO’s job to manage the risk”, but in moments like a global cyberattack, they also carry the blame, the fear and the emotional fallout - often alone.

If we want sustainable security, we have to start treating psychological safety with the same seriousness as system uptime.


r/ciso • • Nov 13 '24

/r/CISO is being rebooted

56 Upvotes

Hi all, this subreddit has become a haven for blog spam and low-quality conversations due to a lack of moderation, so I have stepped in to help clean it up. For now, I have turned off link posts to reduce spam, but may turn that back on down the road. If you have suggestions for rules or information you would like to see here, please provide your feedback.

For now, we have two basic rules:

  • No blog spam or general spam

  • No selling


r/ciso • • 28d ago

For those that left a CISO role, where did you go next?

49 Upvotes

I've been in the big chair a while now and definitely feeling the burnout/impostor syndrome, but I'm making better money than I have in my life. For those that are still here on the sub but left the title, where did you go after and are you happier now?


r/ciso • • Jul 28 '26

Terrified of being personally sued. Help.

42 Upvotes

I'm in a C-suite position (not CISO) at a small company that sells to government, and I am responsible for security. I don't have a background in security whatsoever. We have a SOC 2 compliance tool and have completed audits successfully, but I'm worried our security stance is too weak and that our security questionnaire answers are...questionable, or out of date. Our engineering team is stretched extremely thin and I have a million other responsibilities in my role, so I barely have enough time to enforce compliance basics like policy enforcement or getting vulnerabilities patched. We barely manage to get ready in time for our audits. I've asked our CEO about getting outside help, but she has declined to invest any more money into security due to our poor sales performance, directing funds to other departments. I have had sleepless nights wondering if we're going to get hacked or audited, and that I will be personally sued if our company can't defend itself against a lawsuit. My mental health is tanking and it's starting to make me physically sick. Any help or advice would be appreciated.


r/ciso • • Feb 22 '26

CISO Day in the Life

40 Upvotes

I’m looking ahead at my career options, and the thought of being a CISO is kind of daunting because the CISOs I know don’t really have a life outside of work.

I’m wondering is that the case for all of you? Or is it just the small group that I know?

My overall question is: What are the challenges that you’re seeing when it comes to work life balance? How much of your week(end) does being a CISO actually require?

I feel like every CISO I know is ALWAYS on the clock.


r/ciso • • Jan 24 '25

Nearly half of CISOs now report to CEOs, showing their rising influence

38 Upvotes

The CISO’s rise to the C-suite comes with more engagement with the boardroom, an audience with the CEO, and the power to make strategic decisions for the business, according to Splunk.

82% of surveyed CISOs now report directly to the CEO, a significant increase from 47% in 2023. In addition, 83% of CISOs participate in board meetings somewhat often or most of the time.

While 60% acknowledge that board members with cybersecurity backgrounds more heavily influence security decisions, only 29% of CISOs say their board includes at least one member with cybersecurity expertise.

The report is behind a registration page, but a story with the key findings (with no registration or trackers) is here:
https://www.helpnetsecurity.com/2025/01/24/cisos-board-relationships/


r/ciso • • Sep 01 '26

Does a CISO’s appearance and sense of style matter?

36 Upvotes

Random question, but I’m curious what people think. As a CISO, do you think it’s important to know about fashion, dress well, and generally maintain a polished appearance?

Does the way a CISO looks and presents themselves have any impact on how people perceive their personality, leadership, credibility, or authority? Or is appearance basically irrelevant as long as they’re good at their job?


r/ciso • • Jan 20 '26

Big chance I'm offered the CISO role at my current company... and I'm not ready

36 Upvotes

Well, I've been in the GRC space for the last 4 years from a product management to now more recently information security risk management (DORA, focusing on DR, BCP, Incident Management, Risk Register, Risk Reporting etc)... well you get it, the governance stuff.

And recently, my boss has been hinting that management is planning to make me CISO (from my current role of Security Risk Manager).

1 I do not feel ready, nor qualified, honestly, mostly because I have NEVER been an information security analyst and have never worked on the SIEM, SOAR, DLP, IAM technical parts of information security... although, I have a decent understanding in what happens in most of these verticals... maybe not technically, but conceptually

2 the good thing is that our SOC is outsourced, so, I'm not too sure where I would come in? Oversight of SOC and I'll take over the "GRC part' of being a CISO?

Can anyone guide me as to what I should prepare myself for, I plan to do CISSP very soon...

Thanks!


r/ciso • • May 15 '25

How to keep data safe while using Google Drive, Slack, AI, etc.

35 Upvotes

Hey CISOs, I am working with a client and can use some advice. They are a medium sized, AI-first SaaS with open communication on Slack, and lots of files shared on Google Drive. I know the first step is to do an audit of who has access to what, etc etc but don't really know where to begin.

What are some internal and external things they can do to secure their data?

EDIT: Thanks for all the suggestions! They have moved forward with defining a DLP strategy, shifted towards a least-privilege model, and begun implementing Polymer DSPM for Slack, Google workspace, etc.


r/ciso • • Jul 02 '26

Compliance is not security

31 Upvotes

Heard a worker go on a rant about “compliance is not security”, “checking the box”, “security theater” rant the other day.

It got me thinking… if compliance isn’t security, then what is?

The green dashboards that turn out to be wrong? The pentests that mostly find the stuff you’d have caught yourself if you’d kept your environment patched, updated, and configured? The tools you bought and never confirmed still work?

Feels like half the things we hold up as “real security” only look impressive because the basic compliance work wasn’t done in the first place.

Curious where people actually land on these phrases.

And a real question: is there a difference between an annual compliance audit and continuously checking that your environment actually stays secure all year long? I feel like the second part is where security should actually live. 😅


r/ciso • • Oct 27 '25

If I Started a Blog By a New CISO for new CISOs..?

31 Upvotes

Someone messaged me asking me to give them thirty thousand dollars in exchange for a three month engagement to help with "personal brand awareness." They don't even have any existing client base to give me a reference or to justify why they're worth as much as a new car. It made me mad.

Nobody wants to read another blog. But I'm fairly active on DoD cyber subs and post on other cyber subs from time to time and I get people in my DMs once or twice a week asking questions and looking for mentorship.

And this person got me thinking. I can write. People seem interested in things I have to say. I took some journalism classes in college.

I work at a small software developer, I manage a team of 9 other cyber folks ranging from extremely experienced to just out of college. I have grown into this role over the last 7 years or so and I feel like sometimes I know what I'm doing and sometimes I'm out of my depth.

Would people be interested in, or find it useful, if there was a blog written from the perspective of a new CISO talking about CISO and SMB problems? I mostly want to do it because I'm mad at this random influence peddler but maybe there would be value for other folks to learn from watching me fail and maybe sometimes succeed?


r/ciso • • Aug 15 '26

How to present Threat Intelligence properly to execs????

30 Upvotes

So, to give some background. I lead the threat intelligence program of a major bank. Now we receive tons of IOCs/CVEs and brand abuse/impersonation cases and we do take action on them accordingly.

But whenever we create a presentation, it's always numbers

- no. Of IOCs we received, sources (regulator/commercials)

- social media/brand abuse/impersonation/rogue apps count & takedown status.

But execs don't understand these numbers. How can I present the data such that they are assured that we are safe from any kind of threat & prepared for what's coming in the future.

Been researching lots of things but didn't quite get anything. Would really appreciate your views and guidance here.


r/ciso • • Jul 29 '26

Honest question: Why do you choose to attend paid executive events?

30 Upvotes

There's a whole category of event built on the same trade. Vendors pay to be in the room, security leaders attend free. Curated dinners, executive roundtables, pitch nights, membership clubs in Miami, invitation only summits. The organizer's actual product is access to you, and the only thing that makes that product worth anything is that you decided to show up.

Asking as a first time founder new to being a vendor, I keep receiving a list of big executive names attending these, and asking for sponsorship to get access to a few minutes to pitch.

what makes you say yes to being part of one of these? have they ever produced something of value to you?


r/ciso • • Mar 14 '26

Security questionnaires: 15 questions are more practical and helpful than a 100

30 Upvotes

I spent so many years in cyber security, and I always hated lengthy security questionnaires. I believe that a short and focused 15 questions process can be much more efficient and useful than sending those hundred plus questionnaires or web-based solutions.

Do you relate or think I’m totally wrong?

Happy to share my top 15 if it helps…

Edit -> here's my top 15 👇

I start with a short and simple document request list with the most recent::

  1. High-level data-flow and architecture diagram

  2. Information security policy

  3. ISO 27001 certificate + Statement of Applicability

  4. SOC II Report

  5. Penetration Test executive summary

  6. Vulnerability Assessment executive summary

  7. List of all sub-processors

And my 15 questions:

  1. Please describe the data transfer and integration points between your infra and ours

  2. Please describe where our data is going to be stored, processed and accessed

  3. How many full time security team members do you have?

  4. What are the top 3 security risks applicable to your company and what is the mitigation plan?

  5. Do you conduct background checks to all employees and contractors?

  6. Will our data ever leave the Production infra under any circumstances?

  7. Describe your security monitoring and alerting capabilities

  8. Describe your anti-malware strategy for endpoints and Production alike

  9. Are operating systems, containers and applications hardened based on industry best practices?

  10. Are patches and security updates applied on regular basis?

  11. Describe your Security Incident Response controls and practices and have you suffered an actual security breach in the last 3 years?

  12. Do you enforce 2FA on all Production and Internet facing platforms?

  13. Is SSO and MFA supported within the product?

  14. Do you have a documented and tested Business Continuity Plan?

  15. What Secure Development Life-cycle activities are in place?

I know that the list is lacking a few areas - these are usually given in the ISO and SOC II audit report.
Happy to get your feedback, but based on my experience - this is a real time saver


r/ciso • • Feb 16 '26

Why are Indian grc teams so hard to deal with?

30 Upvotes

I’m not sure if anyone has found this but I’m really struggling operating from the UK and dealing with Indian GRC teams who don’t seem to comprehend that not all businesses opt to have a soc2 audit carried out and that it really isnt particularly applicable to companies providing consultancy services. We have iso27001 and they want to always see full audit reports but can never explain what it is that they’re looking for that isn’t contained within the certificate and soa. It’s like they just have a tick box exercise that feel they have to go through and despite all the evidence, without releasing information that is irrelevant to the service they’re receiving they accuse you of not managing your isms correctly.


r/ciso • • Oct 26 '25

How to detect and prevent shadow LLM usage?

30 Upvotes

Hello, faced the case when big enterprise employees use public LLM, upload there confidential information and produce workslop. Need advice, how can I handle such issues (AI usage policy, some GRC, MDM restrictions,maybe some tools)?


r/ciso • • Oct 10 '26

Moving into my first CISO role at a small fintech in the Middle East — looking for advice from experienced CISOs

28 Upvotes

Hi everyone,

I’ve recently been hired as a CISO for a small fintech company in the Middle East, and I’d appreciate advice from people who have been in similar roles, especially those who have built security programs from the ground up.

My background is primarily in cybersecurity GRC, audit leadership, and regulatory compliance. I’ve led audit teams, managed ISO 27001 and SOC 2 engagements, holds CISM, and worked on regulatory audits involving central banks and other regulatory authorities.

In my new role, the immediate expectation is to design and implement the company’s entire Information Security Management System (ISMS), meet applicable regulatory requirements, and ensure the organization is adequately protected.

I understand the GRC and compliance side reasonably well, but I want to approach this role correctly from a broader CISO perspective, particularly around technical security, operational risk, and building a sustainable security program in a small organization.

I’d appreciate insights on a few things:

  1. First 90 days: What would you prioritize during your first 30, 60, and 90 days as a CISO in a small fintech?

  2. Building the ISMS: How would you approach designing the program from scratch without getting buried in documentation and policies?

  3. Technical security: What technical areas should I personally understand and validate first, particularly around cloud security, IAM, application security, monitoring, and incident response?

  4. Regulatory compliance: How do you balance meeting regulatory requirements with implementing controls that genuinely reduce risk?

  5. Limited resources: If you were the only dedicated security person, how would you prioritize work, leverage existing tools, and decide what to outsource?

  6. Executive expectations: How do you demonstrate progress and communicate security risks to the CEO and board without creating unnecessary complexity?

I want to avoid that and build a security program that works in practice, not just on paper.

For experienced CISOs who have built security programs in fintechs or startups, what would you do differently if you were starting again?

Any practical frameworks, lessons learned, mistakes to avoid, or resources you would recommend would be greatly appreciated.

Thanks in advance!


r/ciso • • Sep 12 '26

Would you be a CISO, a Chief Scapegoat, or something else?

28 Upvotes

Some of these CISO job postings are getting ridiculous.

Look at this one from LinkedIn - Requires 15+ years’ experience, CISSP, CISM and CISA certifications, Fortune 500 experience, leadership through a major security incident, deep expertise in cloud, network and application security, and executive-level business and communication skills. Pay is Senior Manager level - £130K, reports to the CTO, and leads a two-person team.

Here is another one - it's from Lever. The title is literally Chief Information Security Officer and Privacy Officer. The role owns cybersecurity policies and controls while also serving as the organization’s Privacy Officer. Pay is $141,000 to $210,000 annually plus 25% variable compensation. Combining these jobs is not impossible in a small organization. But if one person owns the security-control environment and is also responsible for privacy oversight of that environment, the posting should explain the governance model, independent assurance, privacy expertise, staffing, and authority. Otherwise, it looks like one executive is being assigned responsibility for both building the program and absorbing the accountability when it fails.

This is one from Dice. The title is Chief Information Security Officer / IT Manager. The job requires one person to lead the information-security program, technology operations, cybersecurity initiatives, regulatory compliance, business-continuity planning, and disaster-recovery planning. They would also manage cyber risk, support regulatory examinations, coordinate security across departments, and keep the technology infrastructure secure, reliable, and compliant. I got tired just reading about it lol. $95,000 to $100,000 per year comp! So they want the person responsible for identifying, assessing, escalating, and managing cyber risk to also run IT operations, make the infrastructure decisions, carry the outages, support the regulators, own security, and own continuity planning. This is an IT department, a security department, a compliance function, and a resilience program compressed into one person with a CISO title.

The job market is tough right now, so people are going to throw themselves at these postings, but the endings will be fairly predictable imo.


r/ciso • • Jul 11 '26

Why shouldn’t I just use microsoft

28 Upvotes

Im researching ways to detect and manage shadow ai usage where I work. Im generally a fan of not giving one company too much “control”, but when i research what microsoft defender, cloud detection, purview and intune can detect I dont get why I would pick anything else, given I’m already in their ecosystem?

What are some of the reasons that drove you to pick another provider such as Nudge Security or someone else?


r/ciso • • Jan 07 '25

Path To CISO

28 Upvotes

Hi All, I was curious about anyone in here who is an actual CISO what your path to that position looked like? All of your experience and credentials leading up to qualifying. I am thinking about setting my sights on that path, and am very interested in hearing from you.

For reference,

  • I have around 9 years in cyber compliance/answering security controls (via NIST RMF)

  • Not a lot of hands on experience with utilizing the actual cyber security tools - just dealing with the results and outputs from teams that do use them.

  • I have a Masters Degree in Cybersecurity

  • I have the CISSP, CEH, CHFI, Sec+, Net+, and A+

Regarding experience, what do you think I would need to add? Are there positions that better prime you for CISO that I should be aware of. Would an MBA with a focus on cyber be beneficial?

Thanks in advance!


r/ciso • • Sep 30 '26

How I’d structure authorization for enterprise AI agents without building another IAM stack

27 Upvotes

I’ve been working through how I’d design authorization for enterprise AI agents, and I think there’s a tendency to make this more exotic than it needs to be.

My starting point would be: don’t create a parallel IAM stack just because the actor happens to be an AI agent.

Keep your existing IdP/IGA/PAM/PBAC as the authoritative control plane for identity, ownership, lifecycle, policy and privileged access. What changes is the execution model around the agent.

A few principles I’d use:

1. Give the agent an accountable identity where possible.

Every production agent should have an owner/sponsor, purpose, lifecycle state and attributable execution identity. But don’t assume every agent action will conveniently arrive as a clean service principal. Agents may operate through delegated tokens, other agents, MCP/tools, APIs, or even an authenticated human browser session.

2. Authentication should never imply authority to perform the task.
The useful authorization question isn’t “is this a valid agent?” It’s:
May this agent, acting for this user/service, under this task, perform this exact action against this resource right now?
Effective authority should be the intersection of the agent policy, task authority, delegating principal’s authority, resource policy and current risk/context, not simply whatever permissions the credential happens to carry.

3. Give the agent bounded task authority.

A task should have an issuer, acting agent, permitted actions/resources, expiry and delegation limit. The agent shouldn’t be able to expand its own authority just because its workflow changes.

4. Put enforcement immediately before consequential execution.
Before a tool/API/resource call executes, normalize the requested action and resource and evaluate policy against the exact request.
If the agent can reach the same target using another credential or route that bypasses that enforcement point, assume your enforcement is partial.
This gets particularly interesting with browser/computer-use agents because the downstream application may see a perfectly legitimate human session even though an agent actually generated the action.

5. Avoid standing target credentials where possible.
Broker bounded/short-lived access after authorization rather than giving agents reusable credentials and hoping upstream controls contain them.

6. Treat approval as step-up, not as the security model.
High-impact actions can require approval, but approval should bind to the exact action/resource/request and expire. The agent shouldn’t be able to approve its own request or turn one approval into broader authority.

7. Preserve execution provenance.
For consequential actions, I want to be able to reconstruct:
initiator → agent → task → authorization decision → approval/grant → target request → actual outcome
An IAM log showing that access was granted isn’t enough if I can’t establish what the target system actually executed.

8. Couple agent lifecycle to human and business lifecycle.
If an owner leaves, changes roles, a workflow is retired, or the agent’s purpose changes, that should trigger revocation or recertification rather than leaving another orphaned NHI behind.

To me, this is increasingly the distinction between agent identity and agent authorization/governance. Identity tells us what the agent is. The harder control problem is proving what authority this particular execution had and enforcing it all the way to the action.

I’ve been turning this into a vendor-neutral reference architecture, but these are the principles underneath it.


r/ciso • • Aug 25 '25

CISO with no team, IT wants “IT security” - advice & references?

27 Upvotes

TL;DR

CISO in a multinational (~600 employees), but with zero staff. IT wants to own “IT security”, which means different things depending on what’s convenient (SOC, DLP, firewalls, certifications, etc.), yet they don’t take formal ownership.

The company is great, but this setup feels unsustainable.

I’m the CISO of a multinational (600 employees, multiple countries). IT has ~7–8 people (infra/helpdesk, endpoints, no software/data governance), two of them are security engineers. I report outside IT (separate reporting lines to avoid conflicts of interest).

I have zero staff. IT wants to claim ownership of “IT security” (a term that shifts depending on what’s convenient for the IT manager, sometimes incident response, sometimes SOC, DLP, firewalls, or certifications), but without real accountability. Whenever issues arise, responsibility tends to get deflected back to me, since I’m CISO.

The two security engineers report to the IT manager, who has almost no security background. Any request I make has to go through IT’s ticketing system, so security work competes with IT’s backlog.

My background is mainly in technical security, more recently expanded into GRC. I understand the challenges of IT, security, and compliance, and I try to bridge the gap. But with this setup I feel stuck: responsibility without authority, no team, and unclear ownership.

In every other company I’ve worked for, security was independent from IT. Here, IT resists that split but also refuses full ownership.

I’m not asking for expensive tools, just clarity of scope and responsibilities. I don’t see myself as the kind of CISO who just gives orders from above; I try to understand risks, dig into issues, and maintain a balance so the company can operate with minimal risk given the resources available.

But I don’t feel comfortable, because sooner or later there will be an incident, and accountability will just be bounced around (and most likely, it will fall on me).

The company itself is great, I enjoy working with colleagues, but this situation is the last straw before I consider leaving. The role I accepted was based on assumptions that no longer hold true.

Unfortunately, there isn’t a universally agreed structure for how IT and Security should be organized, every company does it differently. Even major standards don’t provide much guidance on this, which makes it hard to explain to the board why this setup is risky. (To anyone with a decent background and an open mind it’s obvious in 30 seconds, but not to some executives.)

And here are my questions:

  • Would you work under these conditions?

  • What’s the minimum step you’d push for — just clear R&Rs in writing, or a structural change with a dedicated Security function?

  • (Personally, I’m not comfortable with all technical security staying under IT, but if that’s how it must be, I’d at least want it formally written down to protect myself.)

  • Do you know of any authoritative references or frameworks that outline how IT vs Security responsibilities should be organized?

  • Am I looking at this the wrong way, and should I just accept it as normal?