CISO/CSO
Hi Glenn, To get straight to the point, That Director function is defined in a way that is can Not significantly improve the Security level of the organisation. Simply because there is a Catch-22 situation structure, which prevents that the person who gets that role can actually fix/resolve several deeply rooted Security and risk-management flaws. If... you actually want to get a serious improvement of the security/Protection (risk management) structure ? Then... you need to reposition that function to create enough space to actually get some changes past all the managers who will resist such change with force and dirty tricks. First thing that i would do if the position would be placed correctly, is to get rid of a bunch of infiltrated imposters. Specifically some 'security' people who are actually undermining the company security, just to get money out of the organisation for themselves. One of them is Predrag Vuckovic {nl.linkedin.com/in/pvuckovic}, who doesn't even seem to really care about risk-managent basics, because he is clearly giving security sensitive information to criminals and hostile states espionage by publishing such info on the public internet just for self-aggrandizement :( *sigh* Thus making himself and the company extra vulnerable for blackmail/bribes, social engineering, espionage, hacking his own IT devices (which contain access credentials to Booking IT infra), ID Theft, etc... etc.. Glenn, if you care to have a frank chat about it in Amsterdam some time? i've been an operational (chief) security officer for high-risk organisations (.govt & .com) in various countries for 30 odd years. Have dealt with targeted espionage & sabotage and other types of unwanted activities. Have tech know-how of complex infra _ so IT and Sec people can't get away with fancy B.S. excuses when things are wrong, but instead we can look at proper options to correct situations. ~> But most of all, do actually care about pragmatic protection results.. even when one needs to ruffle feathers to get past barriers in order to get the required result. Kind regards, //j --- # jobs.booking.com/test/jobs/30195 # www.consultant.nl/vacatures/vacature/18236/director-central-technology-and-security-safety-fraud-ssf-risk-operations Ps. You may want to ask the current CISO's, if they would kindly provide you with a report on how many Responsible Disclosure and Security Issues emails and phone calls have been Received via various paths. Per each year, for the past 5 years. How many of those have been on status 'unresolved' for weeks/months. And hard data stats on how many of those reported issues where NOT registered in the ISMS systems. Also a clear and honest explanation on: Why a bunch of medium- & high-risk security issues which have been reported, have been blatantly ignored by IT and Security people. [Playing the "Not MY Problem" game..] The honest answer would be something close to: When outsiders report Software bugs and flaws which we understand and think we can fix, then we register it in ISMS and work on it with joy. However, when outsiders report organisational Structural security issues which we don't know how to fix (like a dysfunctional company procedure, or wrong IT product choice by some manager who doesn't want to hear any criticism), then workfloor helpdesk/IT/Sec people prefer to ignore the issue and expect that no one will care that some security incidents have only been possible due to those structure flaws. A few years ago, when working in Amsterdam. I've seen some responsible disclosure type messages which where send to Booking.com about security issues. Which where read by the workfloor people, but they didn't send a response and didn't even bother to ask any questions to provide more details or explanation.
Nog geen reviews. Heb je met anna samengewerkt? Deel je ervaring hieronder.
Laat je gegevens achter, dan brengen we je in contact.