What’s your backup security career plan?

Even the best career planning can go awry. Consider this scenario:

It is your first day back in the office after a great family vacation. It is a couple of weeks before the end of your company’s fiscal year and you are expecting both a bonus and a raise. Life is good.

The plan you created for your security career has really come together well. You had a successful career in government then easily transitioned into a senior security management role in the private sector. The job you are in now is both challenging and rewarding. To top it all off, your boss is a terrific person who you respect and enjoy working for. Two more years and you will be fully vested in your company’s incentive plans. And you are only 56. Life is really good.

You have only had time for one cup of coffee, but just got a call from your boss. You have been asked to join him for a meeting. Well, this is the moment for which you have been waiting. Welcome back! We missed you! Let’s talk about your raise and bonus!

Unless it is not that moment.

The head of HR is also in the room and seems oddly somber. You sit down and hear the words,” We have just finalized an agreement with our foreign competitor, the Super Big Corporation. We are going to merge our operations and form a new, stronger organization. This will provide even greater value to our shareholders.”

The news gets worse. Your position has been eliminated and you will not have a role within the new company. Instead of a conversation about your pay increase and bonus, HR is describing your severance package. You may not have heard everything they were saying. Your mind went to your two children who just started college.

Stories like this are increasingly common. Security practitioners who felt they were in strong, secure positions in their organizations are finding themselves unexpectedly open to new opportunities. This reflects the changing business model and will continue to evolve as merger and acquisition activity rebounds.

The demand for talented security professionals is real. However, the reality is that organizations have a plethora of management roles in comparison to security positions. When companies merge, there likely is room for only one security leader at the top. Despite being a valuable asset to your current corporation, where will you land should your company be acquired?

Given this trend, are you content to wait and see what happens? You can let events like mergers, acquisitions, and downsizing impact your life and shape your career. Or you can take control. You may not be actively looking for another job right now. However, being prepared to execute an effective job search strategy at a moment’s notice should be a backup plan you already have in place.

Next month we will be looking at the best way to create a backup security career plan you can execute should unexpected events occur. Because, no matter how good life is in your current job, time spent considering alternatives will give your career resilience.

https://www.securitymagazine.com/articles/100501-whats-your-backup-security-career-plan




Stephen Ford hired as CISO at Rockwell Automation

Rockwell Automation announced that Stephen Ford is joining the company as Vice President and Chief Information Security Officer (CISO). In this role, Ford will develop and execute a holistic cybersecurity strategy to ensure that the company’s infrastructure, products and customers are secure.

Ford joins Rockwell from McKesson Corporation, where he was Vice President of Global Security. In this role, he led teams overseeing cybersecurity operations, offensive security, incident response, security engineering architecture and access management. 

Prior to McKesson, he held IT infrastructure, information security and compliance, and systems engineering leadership roles at HP, Baylor College of Medicine and The University of Texas Health Science Center at Houston.

Ford also served as the chair for the national board of McKesson’s African American/Black Employee Resource Group, providing support, professional development and growth opportunities for Black professionals. He holds a bachelor’s degree in computer science and an MBA from Prairieview A&M University in Prairie View, Texas, and a master’s degree from Harvard University.

Congratulations!

https://www.securitymagazine.com/articles/100508-stephen-ford-hired-as-ciso-at-rockwell-automation




CISA undertakes new efforts to fortify open source ecosystem

Recently, the CISA held an Open Source Software (OSS) Security Summit where OSS leaders (including industry and federal agencies) gathered and announced a plan of action to bolster the security of the open source ecosystem. This summit recognized the essential services and functions that OSS supports, and so those in attendance aimed to advance the security of its ecosystem.

During the summit, OSS leaders investigated avenues that could boost the open source infrastructure. The result included several key actions that were announced by the CISA.

  • Package repositories will work closely with CISA in order to adopt the Principles for Package Repository Security Developed set forth by CISA and the and the Securing Software Repositories Working Group associated with the Open Source Security Foundation. These guidelines outline security maturity levels that package repositories can follow.
  • An endeavor launched by CISA will open the door for cyber defense collaboration and information sharing among OSS infrastructure operators. The goal is to increase the defenses of the OSS supply chain.
  • Materials from a tabletop exercise performed by members of the summit will be published and made available to the open source community, allowing operators to bolster security and resiliency. 

https://www.securitymagazine.com/articles/100497-cisa-undertakes-new-efforts-to-fortify-open-source-ecosystem




Atlanta chemical manufacturer cited by OSHA

The Occupational Safety and Health Administration (OSHA) cited an Atlanta chemical manufacturer with 67 serious violations and a proposed penalty of $289,439 for exposing workers to a series of workplace dangers associated with chemicals and struck-by hazards.

OSHA found violations for failing to:

  • Provide feasible engineering controls to reduce employee exposures to hexavalent chromium.
  • Establish and implement a respiratory protection program and provide a medical evaluation before workers were fit-tested or required to use respirators.
  • Develop and implement a comprehensive hazard communication program for the handling and use of hazardous chemicals.
  • Provide laboratory employees with information and training on hazardous chemicals in the lab.
  • Provide changing rooms for contaminated protective clothing to prevent cross-contamination of employees’ regular clothes.
  • Provide suitable facilities for quick drenching or flushing of the eyes and body.
  • Use drums and containers that meet appropriate federal regulations for the waste they contained.
  • Ensure chemical drums and pallets were stacked on storage racks in a secure manner.
  • Provide proper training and certification of employees using powered industrial trucks.
  • Develop and implement an energy control program, including written lockout procedures, and training for employees required to perform cleaning and maintenance involving dangerous machinery.
  • Develop and implement a permit-required, confined space program for employees required to enter tanks and vessels.
  • Guard unused portions of a bandsaw to prevent unintended contact with the saw blade.

Workers in the U.S. suffer more than 190,000 illnesses and approximately 50,000 deaths annually related to chemical exposures. OSHA’s website provides an overview of chemical hazards and toxic substances to provide employers and employees with tips to recognize hazards and control exposures.

https://www.securitymagazine.com/articles/100503-atlanta-chemical-manufacturer-cited-by-osha




5 commitments CISOs can make to boost cyber resilience

CISOs have always had a very tough job, but with spikes in virtually every kind of attack, new AI-related risks and a shifting regulatory environment, keeping businesses safe and compliant is only getting more difficult. While there is no way to anticipate every new threat, there are some data-backed ways to limit risk and build lasting resilience against attacks.

Here are five key commitments that CISOs should consider making this year to improve their cybersecurity posture: 

Empower the entire workforce with cyber capabilities

Cybersecurity is not just the responsibility of the cyber team; the whole workforce needs to be adequately prepared for attacks. CISOs and other security leaders should provide opportunities for employees throughout the organization — regardless of role or department — to upskill their cyber capabilities, understand their shortcomings and improve their skill sets. Executives gather data to understand financial performance to fuel decisions — cyber leaders must do the same when it comes to cyber capabilities.

With 80% of cyber leaders uncertain about their teams’ readiness to respond to future attacks, leaders should strive to understand cyber strengths and weaknesses to make more informed decisions and investments in cybersecurity solutions. Employees across the workforce should have access to cyber exercises relevant to their individual responsibilities, an approach that equips leadership with insights into skills gaps. Armed with this data, leaders can be confident that their teams have the knowledge, skills and judgment to respond effectively to cyber threats.

Eradicate blame culture, recognize vigilance

Employees who take part in their organization’s cybersecurity drills or demonstrate security best practices are assets to cyber leaders. It’s important to build a culture that recognizes their diligence whenever possible. At a time when many cybersecurity professionals are considering leaving the industry due to stress, it’s important that employees believe their contributions to cybersecurity are valued. Recognition can take various forms, whether it’s praise during team meetings, awards, or other incentives. Acknowledging employees’ dedication to cybersecurity initiatives motivates them to continue this level of work and positive behavior.

People should also be encouraged to speak up and do the right thing, including escalating threats or mistakes, without fear of losing their jobs. Cyber defense is a team sport, and there is no room for the blame game. Organizations that promote open communication about security concerns — even when an error has occurred — help raise awareness of potential threats and quickly address any security issues, ultimately limiting risk in the long run. 

Double down on secure development best practices

Developers are often tasked with building line-of-business applications at pace without focusing on secure coding best practices. Given the inherent risks to organizations, from vulnerable code to the cost of correcting mistakes later in the cycle, requiring developers to upskill and prove coding efficacy should be mandatory. Security leaders should partner with engineering leaders to implement a secure coding “driving license” check for all existing and to-be-hired developers. Especially in light of developers’ increased adoption of AI, it can potentially lead to unexpected business risks and leave holes in their cyber resilience to leave the door open for exploitation.

Prepare for after-incident response

It’s important to build a team’s cyber capabilities across the MITRE ATT&CK framework. Unfortunately, we often see companies place too much emphasis on preventing attacks, and not enough on what happens after an attack occurs. With breaches more or less inevitable, organizations must implement training and resources to strengthen the cyber resilience of the workforce before, during and especially after an incident.

In an atmosphere that encourages too much time, money and energy to be spent on prevention, security leaders must shift strategies to investing in strategies that empower teams to respond faster and more confidently to emerging threats. By ensuring coverage across all elements of breach prevention and response, you can limit risk and mitigate the impact of a breach. The stronger an organization’s cyber resilience, the better suited they are to prepare for — and respond to — a cyber threat. Just like any skill, cyber leaders should continuously exercise their employees against realistic and emerging threat scenarios.

It’s about preparing, not predicting

We can’t predict the threats and vulnerabilities ahead, but security teams and employees can exercise their skills and stay vigilant to ensure that the impact and cost of these attacks are limited. It is the responsibility of the CISO and security leaders to ensure organizations are moving beyond awareness and instead equipping all employees with the right tools to build the knowledge, skills and judgment to respond effectively. By incorporating these commitments, organizations can be better prepared to report and mitigate cyber threats, boosting cyber resilience and overall security postures in 2024 and beyond.

https://www.securitymagazine.com/articles/100474-5-commitments-cisos-can-make-to-boost-cyber-resilience




Disponibile un tool open-source di threat detection per il cloud


Permiso, fornitore di soluzioni per la cloud security, ha rilasciato CloudGrapper, un tool open-source pensato per individuare la presenza di minacce negli ambienti cloud a opera di gruppi APY.

Basato su cloudgrep, tool command-line per la ricerca dei file log nel cloud, lo strumento esegue delle query sulle attività registrate in cloud per individuare Tattiche, Tecniche e Procedure (TTP) associabili ai moderni gruppi hacker che colpiscono AWS e Azure. CloudGrapper sfrutta le librerie di Permiso sulle attività di detection per essere sempre aggiornato sulle minacce cloud e scoprire immediatamente eventi sospetti.

“Questo strumento open-source eccelle nel rilevamento e nell’analisi di singoli eventi e offre una visione granulare dei potenziali incidenti di sicurezza in agguato negli ambienti AWS e Azure” spiega la compagnia. “In questo modo i team di sicurezza sono in grado di identificare rapidamente e facilmente anomalie specifiche”.

Pixabay

CloudGrappler permette di specificare facilmente lo scope dell’analisi tramite un file .json: gli utenti possono indicare quali bucket e container vogliono scansionare, oppure inserire risorse specifiche. Il file queries.json contiene invece una lista di TTP predefiniti più comuni usati dagli attaccanti; gli utenti possono aggiungere query personalizzate al documento per ampliare la propria ricerca.

Dopo la scansione, CloudGrappler produce un report sempre in formato .json con tutti i dettagli dell’analisi espressi in maniera gerarchica. La gerarchia comprende informazioni quali la piattaforma cloud, il timestamp, il bucket e in ultimo il nome del file coinvolto nell’evento sospetto.

Il report, di facile lettura, consente ai team di sicurezza di individuare velocemente le potenziali minacce senza dover eseguire scansioni manuali; inoltre, la natura open-source del tool consente alle aziende di personalizzare l’analisi in base alle caratteristiche dei propri ambienti e al tipo di minacce ricercate.

Oltre al report, CloudGrappler approfondisce gli eventi individuati indicando chi potrebbero essere i responsabili, il livello di criticità e una breve descrizione dei possibili impatti. Il tool è disponibile per il download su GitHub.

Condividi l’articolo



Articoli correlati

Altro in questa categoria


https://www.securityinfo.it/2024/03/12/disponibile-un-tool-open-source-di-threat-detection-per-il-cloud/?utm_source=rss&utm_medium=rss&utm_campaign=disponibile-un-tool-open-source-di-threat-detection-per-il-cloud




Security leaders discuss Microsoft’s stolen source code

Microsoft’s security team detected a cyberattack in January of 2024. The attack was spotted within corporate email systems, activating an immediate response process, and the source of this cyberattack was identified as the Russian state-sponsored threat actor, Midnight Blizzard. Evidence suggests that Midnight Blizzard is utilizing data gathered from the corporate email system in order to try and gain unauthorized access to the organization’s internal systems, source code repositories and more. 

Security leaders weigh in 

Tim Callan, Chief Experience Officer at Sectigo:

“It’s worth noting that this exploit originates with the same basic credentials compromises that we see in nearly all attacks of this nature. Once the attacker has inappropriate access, a whole host of additional malicious activity becomes possible. Stronger authentication methods, including PKI-based authentication, are our single most powerful defense against these breaches.” 

John Bambenek, President at Bambenek Consulting:

“Whenever something like source code is stolen, incident responders have to start thinking about how that information can be used to attack the organization and customers. Ironically enough, secrets being part of the data being stolen makes this work a little easier. Attackers naturally gravitate towards credentials so defenders can put more strict monitoring on the underlying accounts to look for misuse (after rotating the keys or passwords, of course). That seems to be what’s driving the additional insights Microsoft provided this morning. However, unlike traditional expulsion events in IR where you simply close all the doors opened by an attacker, source code and secret theft requires ongoing monitoring, remediation, and response months after the breach was mitigated.” 

Omri Weinberg, Co-founder and CRO at DoControl:

“Unfortunately, these things will never end and history always repeats itself. Companies, and mostly management teams or boards, need to understand that they must invest more money in their security posture. It’s a never-ending chess game in which you always need to be one step ahead of the attacker.” 

https://www.securitymagazine.com/articles/100498-security-leaders-discuss-microsofts-stolen-source-code




DevOps – leva strategica per il settore sanitario

Gli ospedali e le varie strutture sanitarie, oggigiorno, si trovano di fronte a sfide legate alla cybersecurity in termini di minaccia sia per la sicurezza dei pazienti sia per le loro operazioni quotidiane. DI fatto, la progressiva digitalizzazione dei servizi sanitari introduce complesse problematiche di sicurezza, in particolare per quanto riguarda la necessità di garantire che i dati siano costantemente disponibili, accessibili in modo semplice e conformi agli standard di sicurezza vigenti. In questo contesto, l’approccio DevOps assume un ruolo cruciale nel settore sanitario. Vediamo di che si tratta.

Importanza del DevOps nel settore sanitario

L’introduzione di DevOps nel settore sanitario offre numerosi benefici. Questa metodologia integra lo sviluppo software (Dev) con le operazioni IT (Ops), incentivando una maggiore collaborazione tra i gruppi responsabili dello sviluppo e quelli incaricati della gestione delle infrastrutture. Ovvero, un approccio che migliora significativamente l’efficienza e la rapidità nello sviluppo e nel rilascio di software, permettendo alle strutture sanitarie di adeguarsi prontamente alle variazioni e alle necessità emergenti nel settore.

Vantaggi nell’implementare i DevOps nel settore sanitario

Di seguito si illustrano i principali vantaggi che possono scaturire dall’implementazione di DevOps nel settore sanitario:

  • Riduzione delle spese operative – Sia le spese operative – poiché non ci sono investimenti iniziali in acquisti e formazione – sia le risorse operative sono notevolmente ridotte
  • Integrazione e Distribuzione Continue – DevOps facilita l’integrazione fluida e il deployment di aggiornamenti software e nuove features, assicurando che i sistemi sanitari rimangano all’avanguardia ed efficienti.
  • Efficienza e Scalabilità Migliorate – Le metodologie DevOps permettono alle organizzazioni sanitarie di espandere rapidamente i loro sistemi in risposta alle esigenze in crescita, assicurando al contempo il mantenimento di operazioni senza intoppi.
  • Automazione Accresciuta – Grazie all’automazione, i team DevOps riescono a semplificare i processi, minimizzando gli errori umani e potenziando l’efficienza generale del sistema.
  • Sfruttamento dei dati migliorato – L’architettura di DevOps garantisce una facile accessibilità attraverso le applicazioni a portata di mano per i pazienti e l’amministrazione. I dati vengono sfruttati in più reparti e piattaforme per un utilizzo multiuso al fine di fornire soluzioni sanitarie integrate.
  • Sicurezza dei dati e conformità normativa – Il principio fondamentale di DevOps, i.e. “l’infrastruttura come codice”, consente agli operatori sanitari di integrare i fondamenti della sicurezza all’interno del modulo applicativo stesso. Secondo questo approccio, l’analisi delle vulnerabilità viene eseguita insieme alle implementazioni della pipeline. Ciò consente agli ingegneri di affrontare tutte le potenziali vulnerabilità al momento dello sviluppo e dell’implementazione. Inoltre, viene utilizzato il principio del “privilegio minimo” per assegnare l’accesso. Ciò significa che le macchine e le persone con il livello di privilegio più basso non ottengono l’accesso alle aree critiche del sistema, garantendo la protezione dei dati e il rigoroso rispetto della conformità attraverso la mitigazione del rischio.
  • Aumento del coinvolgimento – Le organizzazioni sanitarie che implementano pipeline Continued Integration (CI)/(Continued Distribution (CD) spesso forniscono funzionalità e soluzioni più personalizzate, con conseguente miglioramento dell’esperienza del paziente (i.e. sistemi di self-check-in che accelerano elaborazione del paziente o compilazione elettronica delle prescrizioni che consentono ai pazienti di accedere ai farmaci da remoto) per un’assistenza immediata e di qualità. Inoltre, anche gli operatori sanitari possono trarre beneficio dai DevOps, ad esempio, implementando la pianificazione automatizzata degli appuntamenti, per migliorare l’efficienza operativa, mantenendo al contempo un’erogazione di cure ottimale.

Team DevOps – ruolo strategico

È essenziale riconoscere il ruolo strategico che i team DevOps rivestono in vari aspetti del settore sanitario, tra cui:

  • Gestione dell’Infrastruttura – Questa è cruciale per assicurare che tutti i componenti infrastrutturali, come server, reti e database, operino in maniera sicura ed efficiente. Ciò include il monitoraggio costante delle prestazioni del sistema, l’identificazione e la risoluzione dei punti critici, nonché l’ottimizzazione dell’uso delle risorse per garantire il massimo livello di prestazioni.
  • Sicurezza delle Applicazioni -Questo compito, che richiede una stretta collaborazione con gli sviluppatori, è rivolto all’implementazione di robuste misure di sicurezza all’interno delle applicazioni. Tra queste, vi sono i controlli di accesso, la crittografia e le pratiche di sviluppo sicuro.
  • Risposta agli Incidenti e Ripristino di Emergenza – L’obiettivo è ridurre al minimo i tempi di inattività e le vulnerabilità del sistema attraverso lo sviluppo e l’attuazione di piani di risposta agli incidenti e strategie di ripristino di emergenza.
  • Principali Rischi per la Cybersecurity nelle Aziende Sanitarie -Con l’avanzamento verso la digitalizzazione e l’innovazione, le aziende sanitarie diventano sempre più bersagli attraenti per i criminali informatici che cercano di sfruttare le vulnerabilità della cybersecurity e sferrare attacchi che possono avere un impatto significativo sull’organizzazione.

In sintesi, l’adozione di pratiche DevOps nel settore sanitario non solo migliora l’efficienza e la reattività delle organizzazioni sanitarie ma gioca anche un ruolo fondamentale nel rafforzare la sicurezza e la resilienza delle infrastrutture critiche di fronte a minacce sempre più sofisticate.

Formazione e sviluppo delle competenze necessarie per adottare efficacemente le pratiche DevOps

È doveroso sottolineare che, per adottare le pratiche DevOps in modo efficace nel settore sanitario, è necessario strutturare una formazione e uno sviluppo di competenze in diverse aree. Per quanto riguarda le competenze tecniche, i professionisti IT dovrebbero acquisire conoscenze nel cloud computing, nell’automazione dell’infrastruttura e nelle tecnologie di containerizzazione. È inoltre essenziale la conoscenza degli strumenti di gestione della configurazione, delle pipeline Continued Integration (CI)/Continued Distribution (CD) e dei sistemi di controllo delle versioni.

Inoltre, per garantire un’efficace implementazione DevOps nel settore sanitario, richiede da parte dei team coinvolti una serie di competenze trasversali, quali: esperienza in materia di sicurezza e conformità, gestione del rischio, capacità di collaborazione e comunicazione, metodologie agili e capacità di problem solving.

Come implementare DevOps nel settore sanitario

Di seguito gli step principali da considerare nell’implementare DevOps nel settore sanitario.

  1. Pianificazione – Il primo passo del processo DevOps è la pianificazione. È necessario esaminare le attività operative e di sviluppo e configurarle in base alla metodologia DevOps. Inoltre, durante questa fase, è necessario controllare anche le risorse tecniche e umane, l’inventario, le linee guida software e le politiche di sicurezza. Ancora, potrebbe essere necessario pianificare riunioni con team diversi ed eseguire la gestione delle attività.
  2. Integrazione continua (Continued Integration – CI) – Il server CI deve eseguire il commit di tutte le modifiche di sistema e dei nuovi moduli di codice nel repository centrale. Ciò consente la condivisione e l’unione del codice tra reparti. Un’efficiente gestione del codice previene anche i ritardi.
  3. Test continui – Il repository condiviso viene continuamente testato per verificarne il funzionamento o meno. Se il test dà risultati positivi, viene inviato alla fase successiva. In caso di test con esito negativo o “inconcludente”, il sistema tenta di identificare l’errore ed eseguendo tale operazione attraverso il proprio database. Ciò permette di verificare se l’errore è noto. Se si tratta di un nuovo errore, il sistema genera un report e crea un evento imprevisto assegnandolo successivamente al team di sviluppo che terrà traccia del problema attraverso un tracker degli incidenti.
  1. Distribuzione continua (Continued Distribution) – Il codice, dopo essere stato testato correttamente, viene distribuito nel sistema di produzione (o nel sistema di sviluppo, a seconda del protocollo aziendale), garantendone una rapida e regolare distribuzione.
  2. Monitoraggio e feedback costante – Il monitoraggio costante assicura che il software funzioni al suo livello ottimale. Di fatto, il sistema invia feedback al team di DevOps e, in caso di problemi nella compilazione, viene generato una segnalazione in tempo reale di incidente che il sistema monitora in modo da tenere traccia degli incidenti.

Conclusioni

DevOps sta emergendo come uno strumento cruciale nel settore sanitario, fungendo da catalizzatore per migliorare sia l’efficienza operativa sia la gestione dei costi delle infrastrutture, oltre ad accelerare i tempi di sviluppo delle applicazioni, facilitare la sinergia tra i collaboratori e massimizzare l’uso sicuro dei dati disponibili.

Le organizzazioni sanitarie devono essere capaci di affrontare le minacce informatiche, proteggendosi dagli attacchi contingenti e futuri. I DevOps, in questo ambito, assumono un’importanza strategica in quanto sono in grado di equilibrare dinamicamente innovazione ed agilità con sicurezza e conformità, senza trascurare l’attenzione verso il paziente e si ritiene che contribuiranno sempre più al miglioramento dei servizi sanitari e, ove necessario, rivolgersi a professionisti del settore in grado di offrire servizi dedicati ed accompagnare i vari attori sanitari lungo il cammino sine die verso la cyberresilience.

Articolo a cura di Federica Maria Rita Livelli, BeDisruptive Training Director/BCI – Cyber Resilience Group/ CLUSIT – Comitato Scientifico /ENIA- Comitato Scientifico /FERMA – Digital Committee/ANRA – Board & Comitato Scientifico

Profilo Autore

Certificata in Risk Management (FERMA/ANZIIF certificazioni Iso 3100:2018) & Business Continuity (AMBCI Certification – BCI, UK; CBCP Certification – DRI, Usa), svolge consulenze in Risk Management & Business Continuity oltre ad effettuare un’attività di diffusione e sviluppo della cultura della resilienza presso varie istituzioni e università italiane e straniere. Ricopre anche il ruolo di Training Director presso BeDisruptive Consulting.

Membro de:
· ANRA (Associazione Nazionali Risk Manager & Responsabili Assicurazioni Aziendali) – Membro Comitato Direttivo
· BCI, UK (Associazione Internazionale Business Continuity & Resilience) – Membro del Conduct Committee
· BCI CYBER RESILIENCE SIG – Board Member
· CLUSIT (Associazione Italiana per la Sicurezza Informatica) – Membro Comitato Scientifico e Gruppo CLUSIT AIXIA
· ENIA (- Ente Nazionale per l’Intelligenza Artificiale) – Membro Comitato Scientifico
· FERMA (Federation of European Risk Management Associations) – Membro of Digital Committee
· UNI (Ente Nazionale Italiano di Normazione) – Rappresentante per ANRA al Comitato Tecnico UNI/CT 016/GL 89 “Gestione dell’innovazione” (ISO/TC 279) (Commissione Tecnica -UNI/CT 016 “Gestione per la qualità e metodi statistici”)

Speaker in numerosi seminari e convegni nazionali ed internazionali in riferimento a tematiche di Business Continuity & Risk Management, Resilience , Change Management, Innovazione, Cyber Security, Facility Management & Procurement e Artificial Intelligence

È altresì autrice di numerosi articoli inerenti alle tematiche di Risk Management & Business Continuity, Cybersecurity e Resilience pubblicati da diverse riviste italiane e straniere. Co-autrice de: Report 2020-2021-2022 -2023-2024 CLUSIT-Cyber Security e de “Lo stato in Crisi” ed. Franco Angeli.

Condividi sui Social Network:

https://www.ictsecuritymagazine.com/articoli/devops-leva-strategica-per-il-settore-sanitario/




Security Industry Collaborates on DEI

.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 }

Since 2022, The Security Foundation (TSF), formerly the International Security Foundation (ISF), has set organizational and industry goals for diversity, equity and inclusion (DEI) efforts. In an industry where 94% of job candidates are men and 70% come from a government background, TSF works to constantly improve its own initiatives and foster cross-organizational collaboration on DEI initiatives in the security industry.

“If improving the diversity of the security profession was easy, it would have been accomplished by now. There are many contributing factors that have led to the overall lack of diversity the profession faces today but, the good news is that positive change can be made,” says Dave Komendat, TSF President and seasoned enterprise security leader.

That positive change is one of The Security Foundation’s priorities with their internal and external DEI efforts. Since 2011, TSF has supported the security industry through impactful grant allocation and leading events, including the annual TSF Dinner, which is held during the Overseas Security Advisory Council (OSAC) Annual Briefing.

As part of TSF’s Strategic Plan, the foundation has accomplished a number of DEI-related goals to support diversity at TSF and in the security industry at large, featuring diverse keynote speakers at the TSF Dinner; sponsoring the OSAC Women in Security and Global Security Pride groups; funding two students’ attendance at the TSF Dinner; and hiring Director of Programs Carly Coaty, who directly manages the organization’s DEI efforts.

“With all of those accomplishments, we’re now focusing on next steps,” Coaty explains. “Today, we’re aiming to create organizational alignment to remove DEI barriers and directly influence industry culture at all levels. We’re also working to develop a talent diverse pipeline and security recruitment initiatives.”

❝

We believe that working together with other peer organizations (and to grow [the DEI Summit Group] annually) is the best way to start to affect meaningful change in the security industry.”
— Peggy O’Neill, TSF Executive Director

In April 2023, TSF hosted the inaugural meeting of Joint DEI Task Force, which was made up of delegates from ASIS, the Domestic Security Alliance Council (DSAC), OSAC, the International Security Management Association (ISMA), and The Security Foundation. In fall 2023, the Joint DEI Task Force expanded to include more delegates and evolved to the DEI Summit Group. The DEI Summit Group worked to identify target audiences for the security industry’s diversity efforts, which they identified as college students and entry-level security professionals. TSF will host the second annual DEI Summit this May in Washington, D.C., where the DEI Summit Group will continue to expand on their DEI strategy.

“Through the leadership of The Security Foundation bringing together other major security entities like OSAC, DSAC, ISMA and ASIS — each of whom were already working on strategies to enhance diversity within their own organizations — we have an opportunity to make some really significant progress,” adds Komendat.

“[We’re] learning from the work that been done by each organization, sharing best practices, [and] developing a common diversity strategy and roadmap that each organization currently involved with TSF (and others who want to engage) can implement (at the pace that is realistic for them),” Komendat says.

TSF’s updated 2023-2025 Strategic Plan outlines further steps the foundation is taking to increase diverse representation in the security profession. Building on TSF’s previous accomplishments in DEI, the organization will continue to prioritize diverse speakers at the annual TSF Dinner and institute regular DEI training for TSF’s board. Externally, TSF is putting DEI requirements for grant recipients in place in 2024, which has already manifested in the awarding of a TSF grant to Girl Security, a nonprofit dedicated to involving women and girls in national security positions. Additionally, TSF will continue its industry collaboration involving DEI through the DEI Summit Group.

“The overarching DEI goal of TSF’s current strategic plan is to ‘promote diversity, equity and inclusion within the security profession through intentional grantmaking and education,’” says Peggy O’Neill, TSF Executive Director. “We set internal and external goals, including committing to annual Board and staff DEI training and achieving 50% Board diversity by 2025, which we proudly achieved a year early… We believe that working together with other peer organizations (and to grow [the DEI Summit Group] annually) is the best way to start to affect meaningful change in the security industry.”

The unique industry position of TSF allows the foundation to connect industry organizations and work towards a meaningful DEI partnership. TSF has achieved a number of its DEI goals already, but the team continues to focus on the work ahead.

“We’re very proud and passionate about what we’ve done, and all the work that is still to be done. Our DEI goals energize us,” Coaty says.

https://www.securitymagazine.com/articles/100499-security-industry-collaborates-on-dei




Improve safety and reduce liability using school security cameras

h3 { font-weight: bold; font-size: 18px; color: #C72026; } .sidebar { Nunito Sans’, Arial, sans-serif; font-size: 15px; text-align: left; padding: 10px; background-color: #F4F5F6; border: 2px #C72026 dotted; border-radius: 10px; } .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}

Modern security camera systems can provide convenience, improve investigations of incidents, and — with the vast improvement of cameras and analytic software — can often help prevent incidents. Safe Havens International’s school safety assessment of more than 9,000 K-12 schools and serving as expert witnesses for the largest school security lawsuits the U.S. to date have helped find ways to get even more benefits from school security cameras. While focused on K-12 schools, the concepts discussed can be adapted to other settings such as institutions of higher education, hospitals and hotels.

TRAINING

Camera footage can show employees the correct ways to perform safety duties and is a powerful way to improve the ability of employees to learn while enhancing retention of information presented. Security camera video can be incorporated into multimedia presentations and web courses to create concise, interesting and informative presentations.

For example, one powerful tool to prevent school safety incidents, reduce student conduct violations and to mitigate litigation is a thoughtful and pervasive focus on effective student supervision. Security camera footage of carefully scripted segments depicting effective placement of personnel, wearing high-visibility vests and actively supervising students during morning arrival and afternoon dismissal is one example of how video can be used to prevent tragedies. Traffic fatalities in school parking lots and driveways exceed deaths from violence and cause nine times more deaths than active shooters. Good supervision also reduces the risk of school violence during these high-risk activities. The use of footage from cameras at high levels facing downward can be very helpful for this type of training.

Being able to shows a jury exactly how employees were trained using security camera footage can make it much harder for attorneys and the expert witnesses they retain to claim that personnel weren’t properly trained.

FIDELITY TESTING

While establishing good procedures and training personnel on how they are to be implemented is extremely important, verifying that actual practice aligns with stated practice is another key to enhanced life safety and risk management. Developing written procedures for periodic spot-checking of how employees follow safety procedures both in person and via security camera spot checks not only clarifies expectations and improves compliance, but also creates powerful documentation.

❝

Camera footage can show employees the correct ways to perform safety duties and is a powerful way to improve the ability of employees to learn while enhancing retention of information presented.”

As an example of how important this can be, numerous lawsuits were filed against a major school bus company after an 18-year driver was arrested for molesting children on his bus. In this case, archived video footage revealed the driver assaulted the students as they waited to leave the bus for 30 days in clear view of the security cameras. The driver knew the cameras were only checked if an incident occurred on the bus, which was rare because he transported kindergarten students. In my experience working many such cases over the years, the driver would likely have sought employment elsewhere if he knew that school bus security camera footage would be spot-checked periodically, making it likely he would be caught if he engaged in this type of behavior.

Spot-checking student supervision, visitor screening, weapons screening, school bus safety practices and other processes and archiving the footage can be a powerful tool to enhance other fidelity testing approaches. While it is important to save footage documenting proper practices, footage depicting employees failing to follow procedures and appropriate corrective action is also important. Utilized properly, this approach can demonstrate above-standard-of-care practices in school safety and create a high degree of credibility for employees and the organization.

These efforts should be detailed in writing, comply with organizational policies and union agreements, and be clearly communicated to employees before being implemented. Employees should be made aware that these efforts are designed to protect them and the organization as well as the people served by the organization. As with body cameras utilized by law enforcement officers, this practice can help disprove false allegations.

Documenting training of personnel with security camera footage combined with periodic fidelity testing clarifies expectations, improves performance of personnel, reduces safety incidents and can create significant barriers to frivolous litigation while preventing loss of public confidence should an incident still occur in spite of prevention measures.

https://www.securitymagazine.com/articles/100500-improve-safety-and-reduce-liability-using-school-security-cameras