gespenstern wrote: » CISO should report to either CEO or even better the board of directors or shared. CISO is a shadow of this role if they report to CIO/IT director. There's an inherent conflict of interests in this chain as CIO/IT director's main goal is availability, but introducing/hardening security controls has chances to break availability or make services less available. The company that doesn't understand that is doomed to get breached eventually.
ITSec14 wrote: » I'm kind of confused by this...security's job is to ensure Confidentiality, Integrity AND availability. How would this break availability? You don't just implement security controls without evaluating it's affect on the business. This is why change management exists. Security's job is to reduce risk to an acceptable level as determined by company leadership.I mean, I know that a CISO typically reports to CEO and/or the board. I just don't understand the conflict itself I guess since security is supposed to be "everyone's job" these days. Just a padawan trying to learn from someone more experienced than I
ITSec14 wrote: » I'm kind of confused by this...security's job is to ensure Confidentiality, Integrity AND availability. How would this break availability? You don't just implement security controls without evaluating it's affect on the business. This is why change management exists. Security's job is to reduce risk to an acceptable level as determined by company leadership. I mean, I know that a CISO typically reports to CEO and/or the board. I just don't understand the conflict itself I guess since security is supposed to be "everyone's job" these days. Just a padawan trying to learn from someone more experienced than I
ITSec14 wrote: » I'm kind of confused by this...security's job is to ensure Confidentiality, Integrity AND availability. How would this break availability?
ITSec14 wrote: » Why not just train the developers on how to write secure code? That would be the true proactive approach.
ITSec14 wrote: » If a company is willing to accept that risk, then security has done it's job and the fault lies on senior management if a breach occurs. Isn't that the language of the CISSP exam? We're more of an "adviser" than a fixer.
infosec123 wrote: » Much easier said than done. You have to remember developers have different skill set levels, plus are always constantly job hopping since they are in demand. Then you get the companies that offshore their software development, whooo boy.. That is the language in the exam, doesnt mean its true in real life. Plus, you will be surprised at the number of companies that have any form of GRC program, let alone a proper GRC program.
UnixGuy wrote: » I don't have experience with this, so I'm just gonna wish you a good luck. If you share with us how you managed to go for such a position and what's your work history, a lot of us here would benefit from your experience
ITSec14 wrote: » Thanks for the input! In my short time in security, I've found that it's a constant battle to get changes approved to enhance security. Either because of lack of management buy in or it would affect business functions. I'm sure every company is different in how they approach this stuff.
infosec123 wrote: » Companies are different, but you eventually realize the struggle you face now is relatively common through many companies. Keep this in mind, being a good CISO or security person in general requires you to be a good sales person, because you are basically selling the threats and vulnerabilities you face to management in order to get approval/funding/whathaveyou. Brush up on those interpersonal skills, those will take you a heck of a lot father in the long run than any of those certs you plan on getting...
t93cobra wrote: » I would be reporting to the Chief Risk Officer (CRO), whom reports directly to the CEO. In my job search, I'm avoiding the positions where IS reports to IT as I've seen the conflict firsthand. IT wants to support the business as efficiently as possible and roll out new software, etc. but they tend to overlook the security aspects in favor of this. Efficiency is good, but you need to make sure the product is secure. Otherwise, you'll have a lot more work to do later on. Since the IT Director is new, they may not have a full grasp of all the systems in place. Therefore, I'm having some troubles coming up with questions for them in my interview. What would be some great questions for a potential CISO to ask the IT Director in an interview?
dhay13 wrote: » What they are saying is right. IT's #1 priority is keeping everyone working where security strives for that but provisions have to be made to secure the network and often that can be counter-intuitive to production. This is where the conflict of interest comes into play. There has to be a balance that satisfies the business needs and often the two sides conflict. As for secure coding, yeah... Kelly Handerhan asked in her CISSP videos, rhetorically of course, who has ever had a programming course that taught secure coding? Deadlines are made and must be met. Adding security delays the process. Ideally security would be built in but is usually duct taped on after the fact.
TeKniques wrote: » Congrats and best of luck! I was going to reply that most likely they wanted you to interview with the IT Director because you two would probably be working a lot with each other.
shimasensei wrote: » Best of luck! Thanks for the insight in the interview / hiring process for a C-level InfoSec position. I think a CISO role is a great career goal for many InfoSec professionals including myself. Just curious, is the company a SMB size or large corporate?