What led you to get involved in multiple CISO communities?

Security & GRCPersonal Development
965 viewscircle icon2 Comments
Sort by:
Director of IT in Software3 years ago

My main reason is the chance to learn from peers and industry leaders and share my experience and knowledge.

SVP, Chief Information Security Officer in Education3 years ago

I like sharing whatever I can to add value. But to me, it's a bidirectional activity. No matter how many years you've been in this industry, there's always something to learn. There's always a different perspective to absorb and I find that bidirectional exchange to be critical, even in terms of my day-to-day operations. 

One of the coolest things that drives me to get involved in different organizations is the sector specializations that appeal to specific populations. For instance, in New York, you find a more financial sector type of perspective. Down here in North Carolina, there's more of a healthcare perspective. On the west coast of the US, you're probably going to find more of an entrepreneurial perspective. Each one of those presents an awesome dynamic to bring together and learn from.

Content you might like

What’s your top barrier to adopting AI-driven pentesting?

Lack of mature vendor solutions43%

Trust in AI accuracy62%

Budget constraints18%

Skills to operate the tools28%

View Results

What are the fundamental leadership capabilities that are needed for an era of exponential technology and AI innovation?

Read More Comments

New privacy laws continue to pass by state/by country.  For companies operating in multiple states and/or internationally, is data localization adding additional costs to your privacy program?

Yes, increased headcount19%

Yes, increased vendor/tool costs58%

Yes, both increased headcount and vendor/tool costs17%

No, no change5%

View Results

If you didn't have to work, what would you do?

Read More Comments

Has anyone drafted an SOW for a cloud-based SIEM with setup, migration, and maintenance? I’m working on a FedRAMP-authorized SIEM SOW, migrating from on-prem Splunk, covering data, searches, alerts, dashboards, and models.  Scope includes Environment Setup:  Cloud provisioning, configuration, testing. Connectors/Parsers: Custom data source integration. Content Development: Rules, use cases, threat feeds. Performance Tuning: Query/index optimization. Runbooks: Operational procedures. Also required: 24x7 support, maintenance, lifecycle and application management, role-based training, and documentation.  Must comply with NIST SP 800-53, CJIS, and FedRAMP Moderate+. Goal: Secure, scalable SIEM for rapid deployment. I may be missing elements, so suggestions are welcome. Please share redacted SOWs or tips if possible.