Research uncovers vulnerabilities in ChatGPT plugins

Research done by the Salt Labs team has revealed three key vulnerabilities linked to ChatGPT plugins. 

The first vulnerability occurred when users installed new plugins. The process of installing new plugins includes a website in which users must approve a code. Once the code is approved, the plugin is automatically installed. The research discovered that malicious actors could exploit this process by delivering code approvals with malicious plugins. This could allow an attacker to gain access to a user’s account.

The second vulnerability was detected within a framework used to develop plugins, PluginLab. During installation, user accounts were not properly authenticated. This could open the door for a malicious actor to insert an unauthorized identification into the account, allowing an attacker to be presented as the user. 

The final vulnerability involved several plugins with open authorization redirection manipulation, leading to an account takeover via the plugin. By sending a malicious link to a user, an attacker could obtain user credentials. 

Researchers on this project informed OpenAI and related third parties of the vulnerabilities, and the issues have since been addressed.  

https://www.securitymagazine.com/articles/100511-research-uncovers-vulnerabilities-in-chatgpt-plugins




Trovate vulnerabilità nei plugin di ChatGPT che espongono dati sensibili


I ricercatori di SaltSecurity hanno individuato due vulnerabilità in alcuni plugin ChatGPT che consentono di accedere ad account su siti web di terze parti e ottenere dati sensibili.

Il chatbot può essere collegato infatti a diverse estensioni che, come dimostrato dall’analisi, possono soffrire di importanti problemi di sicurezza, espandendo la superficie di attacco.

“Quando si utilizzano questi plugin, in realtà si dà a ChatGPT il permesso di inviare dati sensibili per conto dell’utente a un sito web di terze parti e, a seconda del plugin, si dà anche il permesso a questi plugin di accedere ai propri account privati su Google Drive, GitHub e altro” spiegano i ricercatori.

ChatGPT

Pixabay

Il gruppo ha individuato anche una vulnerabilità direttamente in ChatGPT che consente a un attaccante di installare plugin malevoli per conto dell’utente. Poiché l’applicazione non verifica che sia stato effettivamente l’utente a inizializzare l’installazione del plugin, un attaccante può sfruttare il flusso di autenticazione per inviare un link creato ad hoc alla vittima e installare l’estensione malevola con le proprie credenziali.

Il plugin può effettuare tutto ciò che l’attaccante vuole; generalmente si tratta di accedere a tutte le informazioni che la vittima condivide col chatbot e potenzialmente anche credenziali, password o altri dati sensibili.

Vulnerabilità nei plugin di ChatGPT

La prima vulnerabilità dei plugin individuata dal gruppo risiede in diverse estensioni sviluppate da PluginLab, un framework usato dagli sviluppatori per creare plugin di ChatGPT.

La falla riguarda tutte le estensioni del framework che interagiscono con GitHub: quando il plugin viene installato, esso crea un account aggiuntivo sul proprio sito che memorizza le credenziali di GitHub; usando questi dati, l’estensione può accedere a repository privati che contengono secret e codice sorgente.

I ricercatori hanno dimostrato il flusso d’attacco con AskTheCode, un plugin di PluginLab che risponde a domande relative ai repository del proprio account, per esempio per conoscere il contenuto di determinati file. Nel collegarsi a GitHub, AskTheCode genera un codice specifico per ChatGPT che il chatbot usa per connettersi all’account utente sul sito di AskTheCode; l’attaccante, inserendosi nel flusso di autenticazione, è in grado di intercettare la richiesta dell’utente, ottenere il codice che lo rappresenta e usarlo per installare AskTheCode, riuscendo quindi a leggere tutti i repository della vittima.

Questo attacco non richiede l’interazione dell’utente ed è presente in dozzine di plugin di PluginLab. I ricercatori hanno contattato la compagnia dietro il framework, la quale ha confermato che, al momento, non ci sono state compromissioni di dati utente.

ChatGPT

Pexels

La seconda vulnerabilità è molto simile alla prima e affligge numerosi plugin di diversi vendor. Le conseguenze di un attacco di successo sono le stesse, anche se in questo caso è necessaria l’interazione utente.

Similmente al primo bug, anche in questo l’attaccante può intercettare il flusso di autenticazione durante l’installazione creando un redirect_uri malevolo per il login e inviandolo alla vittima, generalmente via email; se questa clicca sul link, l‘attaccante ottiene il codice di autenticazione della vittima e può prendere il controllo del suo account.

I GPTs

I ricercatori hanno analizzato i plugin a luglio 2023, prima che OpenAI introducesse i GPTs, ovvero versioni personalizzate del chatbot realizzate dagli sviluppatori. Simile ai plugin, questa feature risulta più sicura e risolve molti dei problemi di sicurezza delle estensioni base.

Le versioni custom di ChatGPT non sono comunque esenti da pericoli e, sottolineano i ricercatori, è essenziale che gli utenti stiano sempre attenti alle informazioni condivise col chatbot e non scrivano credenziali o altri dati sensibili in chat.

Contattati da SaltSecurity, i vendor dei plugin vulnerabili hanno risolto le vulnerabilità e aggiornato le versioni delle estensioni. Il consiglio è come sempre quello di mantenere aggiornati i plugin, installando sempre l’ultima versione stabile.

Condividi l’articolo



Articoli correlati

Altro in questa categoria


https://www.securityinfo.it/2024/03/14/trovate-vulnerabilita-nei-plugin-di-chatgpt-che-espongono-dati-sensibili/?utm_source=rss&utm_medium=rss&utm_campaign=trovate-vulnerabilita-nei-plugin-di-chatgpt-che-espongono-dati-sensibili




Tap into connection points between security and privacy

.w3-panel:after,.w3-panel:before { content: “”; display: table; clear: both } .w3-panel { padding: 16px } .w3-panel { margin-top: 16px; margin-bottom: 16px } .w3-leftbar { border-left: 6px solid #58526F!important } .w3-sand,.w3-hover-sand:hover { color: #58526F!important; background-color: #f1f0f4!important } .w3-large { font-size: 20px!important } .w3-xlarge { font-size: 28px!important } .w3-sans-serif { Nunito Sans’,Arial,sans-serif } .w3-opacity,.w3-hover-opacity:hover { opacity: 0.60 }

Data privacy and information security are both critical components of building customer trust for organizations. Privacy protects our personal data and empowers us to control its use, while security shields information against unauthorized access and threats. Balancing these needs is key, like finding the sweet spot between convenience and robust protection.

In the face of challenges posed by emerging technologies, evolving regulations and the escalating volume of data, privacy and security teams often find themselves stretched thin. To address these issues effectively, enterprise leaders can better leverage the intersections between privacy and security disciplines. By doing so, they not only enhance performance in both areas but also strengthen their overall approach to safeguarding sensitive information. It is crucial for leaders to actively seek connection points between these disciplines, fostering collaboration and ensuring a holistic approach to data protection.

Transparency and trust are vital foundations; organizations must be clear about data practices, while individuals can strengthen their defenses through safe online habits. The connection between security and privacy are evident in ISACA’s recently released Privacy in Practice 2024 survey. According to the survey, data breaches rank among the top three privacy program failures alongside inadequate training and lack of privacy by design. Failing to secure customer data can lead to severe consequences that may lead to privacy violations for affected customers. This in turn, may also expose organizations to regulatory peril and possible long-lasting reputational damage.

Still, the distinctions between privacy and security can often be muddled. Vice Vicente addressed the distinctions well in an AuditBoard blog post, writing “privacy-relevant information usually ties back to a human being. Meanwhile, under security, you might have sensitive data that has to do with a company’s metrics or strategy. Although company information is sensitive, it does not necessarily have an impact on the privacy of the individual, their identity, or their data.”

❝

While there are distinctions between security and privacy, fostering initiative-taking, intentional collaboration between the teams can yield better results for both disciplines.”

Information security encompasses additional imperatives, including data recovery and managing incident response repercussions. In contrast, privacy teams spend substantial time addressing legal and compliance mandates, especially in the context of evolving privacy regulations.

While there are distinctions between security and privacy, fostering initiative-taking, intentional collaboration between the teams can yield better results for both disciplines. Sharing a detailed data inventory is one example. Providing a clear understanding of what data is collected and maintained by the enterprise is crucial for both privacy and security functions, particularly in handling personally identifiable information. There also are technical areas in which security teams can leverage sound privacy protocols. According to the ISACA Privacy in Practice survey, for those whose organizations embrace privacy by design, half or more use more privacy controls than are legally required, leading to cryptographic protection (59%), data minimization and retention controls (54 percent) and improved data quality and integrity (50%). These methods can make the job of security professionals more straightforward and achievable.

Ongoing collaboration between privacy and security professionals is especially key in executing enterprise projects and initiatives. That is why both functions should be represented on a cross-functional taskforce (for enterprises large enough to have dedicated security and privacy functions). By having representatives from privacy, security and related digital trust fields represented, the organization can drive toward holistic approaches to leveraging technology effectively, responsibly and ethically, while also keeping key compliance considerations top-of-mind for all stakeholders. Cross-functional taskforces play a pivotal role ensuring that security and privacy are considerations are integrated from the outset of projects and product development, minimizing the risk of costly recalibrations or remediations in later stages.

Although cybersecurity has been a hot-button issue and dominated discussions among enterprise leaders for nearly a decade, the imperative to prioritize data privacy has gained momentum in recent years, particularly with the introduction of regulations like GDPR and similar regulatory requirements taking root across the globe. While security and privacy interests share some overlap on the Venn diagram, there are distinctions that call for practitioners with specialized expertise. Collaboration between security and privacy professionals can significantly enhance the impact of their work by fostering a connection between functions and moving away from siloed approaches. Joining forces on comprehensive data inventories, developing a shared understanding of necessary actions needed to protect critical data and committing to an ongoing knowledge exchange will allow security and privacy professionals to navigate their increasingly challenging roles with greater efficiency and effectiveness.

Ultimately, a proactive and collaborative approach, involving everyone from security to privacy to IT teams to users, is crucial to forging a secure and privacy-conscious digital future.

https://www.securitymagazine.com/articles/100506-tap-into-connection-points-between-security-and-privacy




What makes a great security leader?

From my interviews across the security field, I have learned that the keys to successful leadership stay the same no matter the sector. In my conversations with dynamic security leaders, I have heard stories time and time again about the impact teamwork and mentorship can have on a security program and the enterprise as a whole.

In my conversations with the 2023 recipients of Security magazine’s Most Influential People in Security award, I asked each awardee to reflect on their proudest career achievements. Matthew Horace, Chief Security Officer at Pretium and Progress Residential, put it well when he said, “My greatest accomplishments are what I’ve been able to do for others.”

As he spoke about giving career advice to burgeoning security professionals and advancing new leaders in the field, I was struck by yet another security leader with numerous significant accomplishments under their belt — in Horace’s case, an impressive career that spans the federal government, Dominion Voting Systems, Mayo Clinic and more — that defined their career success as what they’ve given to others. Horace is not alone in this sentiment — I’ve lost count of how many security executives credit their success in security to their own mentors and commit themselves to passing on their knowledge.

At the 2023 SECURITY 500 Conference this past November, a panel of seasoned security executives including J. Nicole McDargh of Domino’s Pizza; PepsiCo North America’s Steven Antoine; Shannon Fariel-Mureithi of ChildFund International; Tammi Morton of UnitedHealth Group; and Starbucks Coffee Company’s Cheryl Steele discussed the importance of engaging future leaders and training them to prioritize resilience when faced with the security threats of tomorrow.

These five titans concluded the conference day with a candid, open conversation about their responsibility to shape and upskill the next generation of security talent. By giving opportunities to early- and mid-career professionals, security leaders can instill trust in their teams and develop a program that functions as a whole, rather than one leader lifting the weight of the group.

Through encouraging active teamwork and mentoring future leaders, today’s chief security officers are preparing the field for a resilient future — and demonstrating leadership lessons that can apply across all sectors.

With that, I must share that I am moving to a new opportunity outside of Security magazine. Working with the wonderful team behind Security and establishing connections across the physical security and cybersecurity professions have been some of the joys of my time at the helm.

Thank you to all of the security leaders willing to share their own insights for the good of the industry, their organizations, sectors and nations. I look forward to seeing the field continue to grow, evolve and support the mission of safety and risk management across the globe.

https://www.securitymagazine.com/articles/100504-what-makes-a-great-security-leader




DDoS attacks reach critical levels in 14 seconds

Distributed denial of service (DDoS) attacks were analyzed in a recent report by Link11. The report found a 70% increase in DDoS attacks, with attacks reaching critical levels in 14 seconds on average, compared to 55 seconds in 2022. Additionally, two thirds of observed traffic is machine-based, indicating the prevalence of bot activity.

Geopolitical tensions globally contributed to a rapid escalation in DDoS attacks, particularly targeting critical infrastructure, public institutions, and political organizations. The ongoing conflicts fueled politically motivated DDoS attacks by organized groups.

The report points out the heightened security risk posed by web applications and APIs, exacerbated by critical vulnerabilities in unpatched software. The EU’s mandate for Apple to open its interfaces to third-party providers further intensifies the need for enhanced security measures in this area. Moreover, the rising threat from AI-driven bots presents significant challenges, with projections indicating a 131% surge in online bot fraud by 2027.

Read the full report here.

https://www.securitymagazine.com/articles/100513-ddos-attacks-reach-critical-levels-in-14-seconds




L’Europa approva l’AIA, il primo regolamento al mondo sull’Intelligenza Artificiale

Dopo due anni di negoziazioni, l’AI Act è realtà: con 523 voti favorevoli, 46 contrari e 49 astensioni, il Parlamento UE ha approvato il nuovo Regolamento Europeo sull’Intelligenza Artificiale.

L’esame parlamentare non sembra aver apportato modifiche significative al testo votato dal Coreper lo scorso febbraio.

Confermati il generale approccio risk-based, gli obblighi di trasparenza a carico dei fornitori di servizi, l’introduzione dell’AI Office presso la Commissione e il divieto per le autorità statali di utilizzare tecniche di “social scoring”, predictive policing o riconoscimento biometrico nei luoghi pubblici.

Permane anche l’esclusione dal raggio applicativo del Regolamento dei sistemi impiegati a fini militari e di difesa nazionale, come pure degli strumenti usati per scopi di ricerca scientifica o rilasciati sotto licenze free/open source, a meno che non presentino particolari rischi ovvero rientrino nella definizione di General Purpose AI (GPAI).

Secondo il correlatore del Regolamento, l’eurodeputato italiano Brando Benifei, si tratta della “prima regolamentazione a livello internazionale che indica una chiara strada verso uno sviluppo dell’IA sicuro e basato sull’essere umano”.

Sebbene l’AIA sia effettivamente il primo atto normativo formalmente approvato in materia, la corsa alla regolamentazione dell’Intelligenza Artificiale ha visto negli ultimi tempi l’adozione di numerosi standard tecnici e linee guida di organismi sovranazionali, testimoniando il comune sentire rispetto all’esigenza di individuare regole comuni rispetto a una tecnologia che esercita il proprio potenziale trasformativo pressoché in ogni ambito dell’esistenza umana.

L’ultimo passaggio di questo lungo iter è previsto ad aprile, quando il Consiglio europeo dovrà pronunciarsi sulla versione finale.

A partire dalla pubblicazione nella Gazzetta Ufficiale dell’UE, decorreranno poi i 24 mesi al termine dei quali il Regolamento sarà pienamente applicabile in tutti gli Stati membri dell’Unione; un periodo piuttosto lungo, inteso – come già per il GDPR – per consentire ad aziende e Pubbliche Amministrazioni di adeguarsi a una disciplina estremamente pervasiva, ridefinendo le proprie policy e individuando le nuove figure richieste.

Sono tuttavia previste anticipazioni per alcuni divieti, codici di condotta e norme generali, nonché per gli obblighi relativi ai sistemi d’Intelligenza Artificiale “ad alto rischio”, che entreranno in vigore rispettivamente dopo 6, 9, 12 e 36 mesi dalla definitiva approvazione dell’AI Act.

A cura della Redazione

Condividi sui Social Network:

https://www.ictsecuritymagazine.com/notizie/leuropa-approva-laia-il-primo-regolamento-al-mondo-sullintelligenza-artificiale/




QNAP systems announces patches for several vulnerabilities

QNAP systems has released patches with the intent to address multiple vulnerabilities influencing its products. This includes a critical-severity bug potentially leading to unauthenticated device accessibility, allowing users to compromise systems security through a network. The released patches have solved the issue. 

Security leaders weigh in

Casey Ellis, Founder and Chief Strategy Officer at Bugcrowd:

“NAS software is incredibly complex, and complexity brings with it the increased likelihood of vulnerabilities. It’s good to see that QNAP are being proactive about patching and alerting on these bugs. However, it is equally important that users of “easy to set-and-forget” products, such as NAS devices, be diligent about installing them. Or, even better, configuring automatic updates whenever possible.”

Bud Broomhead, CEO at Viakoo:

“As IoT devices often are, QNAP NAS devices reside in many parts of an organization and often are managed outside of IT.  While QNAP deserves credit for finding and issuing patches ahead of vulnerabilities being exploited, there will likely be a significant time lag before QNAP devices in the field are secured. 

Because QNAP NAS devices are high volume IoT devices deployed outside of IT, knowing that you have them and where they are can often be a challenge. Using agentless asset and application-discovery solutions can give organizations a huge advantage in addressing these threats.  

One might ask why with a high severity score QNAP does not simply force the patch to be updated on all devices.  That’s the problem with IoT devices; patching often needs to be scheduled and coordinated so that downtime does not impact operations (you don’t want to take the NAS drive offline if it’s supporting heart surgery).  Automated IoT patching mechanisms where the end user can set schedules for updates is what is needed to ensure threat actors can’t take advantage of these vulnerabilities.”
 

https://www.securitymagazine.com/articles/100507-qnap-systems-announces-patches-for-several-vulnerabilities




GravityZone CSPM+ di Bitdefender automatizza e migliora la sicurezza del cloud


Bitdefender ha presentato GravityZone CSPM+, una soluzione di Cloud Security Posture Management (CSPM) per monitorare e gestire le configurazioni delle infrastrutture cloud come AWS, Google Cloud Platform e Microsoft Azure.

GravityZone CSPM è pensato per aiutare le imprese a gestire gli ambienti cloud pubblici e le crescenti complessità che comportano. Le aziende faticano a gestire l’aumento dei rischi di sicurezza legati a errori di configurazione e all’accesso autorizzato alle risorse.

“I criminali informatici prendono di mira gli ambienti cloud sfruttando gli errori di configurazione, applicazioni prive di patch e utenti con privilegi eccessivi: utilizzano qualsiasi mezzo per farsi strada” ha dichiarato Andrei Florescu, presidente e general manager di Bitdefender Business Solutions Group. “GravityZone CSPM+ estende le funzionalità di sicurezza, gestione della configurazione e IAM alle infrastrutture cloud su un’unica piattaforma, consentendo alle aziende di mitigare in modo proattivo i rischi e rafforzare la sicurezza generale. Poiché la superficie di attacco continua ad espandersi, la gestione delle configurazioni cloud e la visibilità dei privilegi delle identità con accesso alle risorse aziendali sono fondamentali in una strategia di difesa approfondita, così come la difesa da malware e altre minacce convenzionali”.

Pixabay

La soluzione di Bitdefender offre rilevamento delle risorse e gestione della configurazione cloud senza agent, oltre al CIEM per la gestione delle identità su istanze cloud, serverless computing, storage e dati in ambienti cloud multipli e ibridi. GravityZone CSPM+ comprende protezione avanzata degli endpoint, tra cui EDR e XDR, sicurezza dei container con supporto run-time e indipendenza dai moduli del Kernel Linux, più la sicurezza per server, hypervisor e ambienti virtualizzati.

La soluzione garantisce che le identità che accedono alle risorse siano valide per applicare le policy stabilite, rispettare la conformità normativa e contribuire a ridurre al minimo il rischio di sfruttamento da parte di criminali informatici.

GravityZone CSPM+ è in grado di rilevare in automatico le configurazioni errate e le violazioni dei diritti degli utenti negli ambienti cloud, automatizzando anche il reporting. La soluzione supporta il modello Zero Trust con identificazione di identità con privilegi eccessivi e comportamenti di accesso anomali.

Infine, GravityZone CSPM+ fornisce modelli pronti all’uso e mappatura plug-and-play dei controlli tecnici su vari servizi cloud per ridurre le ore di lavoro dei team necessarie alla stesura di reportistica normativa. Bitdefender GravityZone CSPM+ è immediatamente disponibile.

Condividi l’articolo



Articoli correlati

Altro in questa categoria


https://www.securityinfo.it/2024/03/13/bitdefender-annuncia-una-nuova-soluzione-di-cloud-security-posture-management/?utm_source=rss&utm_medium=rss&utm_campaign=bitdefender-annuncia-una-nuova-soluzione-di-cloud-security-posture-management




Developing a security coaching tree

.w3-panel:after,.w3-panel:before { content: “”; display: table; clear: both } .w3-panel { padding: 16px } .w3-panel { margin-top: 16px; margin-bottom: 16px } .w3-leftbar { border-left: 6px solid #58526F!important } .w3-sand,.w3-hover-sand:hover { color: #58526F!important; background-color: #f1f0f4!important } .w3-large { font-size: 20px!important } .w3-xlarge { font-size: 28px!important } .w3-sans-serif { Nunito Sans’,Arial,sans-serif } .w3-opacity,.w3-hover-opacity:hover { opacity: 0.60 }

Former NFL coach Bill Parcells’s coaching tree — consisting of assistant coaches who went on to become head coaches in their own right — is legendary. Parcells hired and trained Bill Belichick among 14 head coaches who have collectively won nine Super Bowls. One of today’s most powerful coaching tree branches out from Chiefs head coach Andy Reid, who himself sprouted from the legendary Bill Walsh tree.

Does the corporate security world have its own version of coaching trees — chief security officers (CSOs) whose deputies or other staff went on to become heads of security or executive leaders at the same organization or elsewhere? I revisited my 30 years of working with corporate security departments and consulted with experts with extensive knowledge of corporate security leadership to find out.

Opinions differ, but the upshot is that coaching trees may not be as prevalent as one would expect. “I’m not sure there is a… coaching staff tree in the security world today,” says Scott Lindahl, the CSO of the Kellogg Company and the President of ISMA. “With so many CSO roles being filled by second-career folks (post-FBI, Secret Service, etc.), there hasn’t been a great bit of a succession planning and development to the CSO role.”

If there are analogs to the Parcells and Walsh trees, they might be ones that started with either the late Don Walker or Ray O’Hara. Many of today’s leaders ascended under their tutelage.

To the extent they exist, one of the most bountiful trees emerged from Baker Hughes starting almost two decades ago. Russ Cancilla hired a bumper crop of talent, including, among others, Joe Olivarez, Brian Hogan and Joe Walters. After more than a decade rising through the ranks at Baker Hughes (and helping to recruit some of the aforementioned professionals), Olivarez now serves as CSO and VP, Operational Center of Excellence for Jacobs. Hogan followed his stint at Baker Hughes by landing senior roles at major corporations; he’s now CSO at LyondellBasell. Walters leapt from Regional Director, North America at Baker Hughes to become the top security executive at NRG Energy.

During the same time period, Capital One had a remarkable run of deputies who are CSOs today. Don Childers (now with PayPal), Dave Aflalo (McKesson), Steve Braden (Comerica), Patrick McCarthy (SlapShot Entertainment), Sean Turner (TD), and Sarah Slenker (Gartner) were among those minted by the bank under CSOs Tim Janes and Timothy Rigg.

❝

It’s not just about the technical ability of the craft. It’s about prioritizing real relationships, learning how to connect, to influence…”
— Joe Olivarez, Chief Security Officer at Brennan and Jacobs

At Target, Brad Brekke begat Bill Tenney (MetLife), Nick Lovrien (Meta), Mike Rackley (Nike), and Craig D’Souza (confidential employer).

Still, Lindahl says he sees relatively few deputies get CSO opportunities at other organizations. One exception has been Marco Mille’s direct reports at Siemens, he says.

Are Baker Hughes, Target, Siemens and Capital One the rare exceptions? What accounts for such runs of talent? Is it careful recruiting, incentivizing, and development? Is it that opportunities are limited at many companies, so the best professionals leave? Is it a matter of luck or happenstance? Why don’t companies with dozens of senior security executives churn out more senior security executives?

It’s likely a combination of mindful recruiting/development, limited opportunities, happenstance and other factors.

Executive recruiter (and fellow columnist) Jerry Brennan says that security coaching trees may not be as obvious or cohesive as NFL coaching trees due to head coaches having much more influence and authority on their teams than security professionals have in their corporations. A CSO may groom a successor, but executive management might have someone else in mind, or wish to move or overhaul the security department once the incumbent CSO leaves.

In addition, Brennan says, “CSOs might repress their deputies. They may not want them to succeed [for fear of getting replaced] or it may not be intentional — deputies are just not paid attention to.” Ignoring assistant coaches in football, by contrast, rarely leads to a successful season.

Moreover, it’s easier to measure the success of a coach than of a CSO. Wins and losses are simpler to assess than losses prevented or other, perhaps murky, metrics.

Brennan and Jacobs CSO Joe Olivarez agree the most fertile environments for security professionals is where the senior security executive “leads up”’; that is, communicates with and provides value to business line owners and executives in other departments.

For example, Olivarez recalls advising Jacobs executives on centralizing Health, Safety and Environment departments in light of company divestitures. “They bought into that idea — not just my boss, but the COO and CEO.”

Unfortunately, Brennan says, many CSOs are “mentally siloed. They don’t understand the infrastructure of the company — administration, purchasing, supply chain, vendor management.”

Adds Olivarez, “Can you run a budget, influence a board, interconnect with enterprise risk?” The best developers of security talent assist their protégés with these non-security skills, he says.

He credits his development to Cancilla, who set him up to report to business leaders. “If you can’t deliver to those operational leaders as a business enabler, you aren’t going to last.”

Olivarez says his purpose as a leader is to help others grow, as Cancilla did with him.

“I prepare them for being in a position to compete for a CSO role,” Olivarez says. “It’s not just about the technical ability of the craft. It’s about prioritizing real relationships, learning how to connect, to influence…. It takes time and willingness.”

CSOs might look to successful coaches like Mike Shanahan, Andy Reid, and Bill Walsh. The Xs and Os of game play are just a fraction of what they do. Like security professionals, they must also motivate, communicate effectively with superiors, navigate adversity, deal with public scrutiny, protect their staff, and convey positive influence.

That’s their legacy. What will be yours?

https://www.securitymagazine.com/articles/100502-developing-a-security-coaching-tree




Making Security a Priority From the Start

For many security practitioners, security is something handed to them as a fait accompli. It was already there when they started, or the decision was made by others on what systems to go with — whether that is a consultant, architect or a different department.

But what if you are lucky enough to be able to get in on the ground floor, to help design a building or retrofit with physical security in mind from the beginning? Would that make your life easier or better?

Brivo recently conducted a survey on “Security by Design,” polling architects, engineers and construction practitioners to find out if security is a priority for them; how much time and money they spend fixing problems after the fact and what that means for others working on new projects. In general security is a top priority for these disciplines, coming in at No. 3, behind sustainability and safety.

However, according to the report, there was  a “disconnect” between what architects and engineers say about integrated security and what it actually looks like “in practice.”

The report’s executive summary explained: “The good news is that the industry is heading in the right direction — it understands its customers’ priorities and is working towards meeting their increased security demands. But it can’t get by on attitude alone. Fully integrating best practices and getting security right the first time is the only way to fix this.”

In fact, NOT doing it has a cost. 

“While it varies, some security costs added post-build, are as high as 20 percent of a project’s budget, and add a week or more to construction time,” the report stated.

Many of the survey results are promising. Currently 56 percent of architects and engineers say they have an established security integration process and 41 percent actively have a plan in place. What’s more, of those not currently prioritizing physical security in the design process, almost all — 98 percent — expect this to change within the next five years. 

But post-construction, there are often still issues, and many AECs expressed some inconsistencies when it comes to the practice of integrating security in the design phase, sometimes resulting in “substantial time and financial investments in rectifying issues long after the initial design.”

Approximately one-third cited significant issues with security integration planning.

The report’s call-to-action suggests that AEC practitioners enhance the integration of security during the design stage. 

“Despite the industry’s expressed commitment to making security a fundamental part of design, visible challenges persist in the integration of physical security in building design,” the report stated.

Here are six best practices gleaned from the survey to get optimum results:

  1. Make sure AECs are certified and trained on courses like CPTED (Crime Prevention Through Environmental Design), which can give practitioners a grounding in best practice. 
  2. Specialized networks like the ICA (International CPTED Association) help AECs to network and get better understanding of how security principles can be applied.
  3. Work more closely with technology providers of access control, CCTV, and other security technologies to learn how their technology is best applied and how it can be most effective.
  4. Make sure design briefs are clear and achievable.
  5. Educate yourself as the customer to make sure you fully appreciate the importance of designing integrated security in the planning stage rather that as something that can be patched in later. 
  6. It is important for AECs to closely examining processes and to do post-mortems of projects where issues have arisen, can help to make these processes better. 

Perhaps the most important lesson to learn from this study is the importance of being part of the conversation from the earliest stages whenever possible; vetting your expert architects, engineers, consultants and integrators to make sure they are on board and aware of security-by-design; and making security integration a priority from the start.

https://www.securitymagazine.com/articles/100510-making-security-a-priority-from-the-start