False Pretences, Shields Up, Same Tools-Different Uses, Big Steps Forward, Trust Issues, and Malevolent Squatting. It's CISO Intelligence for Wednesday, 4th June 2025.
Thoughts for today: Practising to deceive, no way in, cutting-edge mining, next-level protection, proceeding with extreme caution, and easing on down the wrong road.
💡
"Gives me everything I need to be informed about a topic" - __UK.Gov__
Table of Contents
1. Crocodilus: The Sneaky Caller in Your Pocket
2. Account Lockout Policy: When Your Password Plays Hard to Get
3. Cryptojacking Follies: When Your DevOps Tools Go Rogue
4. OpenAI’s GPT-5: The New Sheriff in AI Town
5. The Crown Jewel of Certificates: Chrome’s No-Show for Misbehaving Authorities
6. The Devil Wears Command Lines: Backdoors in Python and NPM Packages
Sign up for CISO Intelligence.
21st century industry insights for the modern CISO
It won't hurt, I promise.
Email sent! Check your inbox to complete your signup.
No spam. Unsubscribe anytime.
Crocodilus: The Sneaky Caller in Your Pocket
_Who knew your contact list had a secret second life?_
What You Need to Know
The latest Android malware, Crocodilus, has been discovered adding fake contacts to users' devices, allowing attackers to spoof trusted callers. This malicious software threatens not only personal privacy but also corporate information security, necessitating immediate preventive measures. Executives and board members are advised to ensure security policies are updated and educate employees on this new threat vector.
*
CISO focus: Mobile Security, Malware Protection, User Awareness
Sentiment: Strong Negative
Time to Impact: Immediate
*
When Your Android Becomes a Crocodile Hunter
In the quest to make our digital lives as seamless as possible, we often forget how inviting our phones could be to sinister elements lurking on the internet. Android malware, Crocodilus, has brought about the latest scare by implanting fake contacts into user devices to impersonate trusted contacts. This strategy is not just a tech travesty; it's a potential business downfall.
The Rise of Crocodilus
Crocodilus, aptly named after the ancient predator, slithers unnoticed onto Android devices, creating fake contacts indistinguishable from the real ones. Users remain unaware as their trusted contact list becomes a gateway for manipulated communications. This malware's subtlety is matched only by its effectiveness at slipping undetected past supposed security measures. Once embedded, it enables attackers to engage with users, posing as legitimate and trusted contacts, leading to fraudulent data exfiltration and security breaches.
How It Works
Contact Manipulation : Crocodilus covertly inserts fake contacts that look eerily similar to existing ones. This allows attackers to pose as colleagues, friends, or service providers.
Data Breaches : The malware can exploit these trusted facades to extract sensitive data, request financial transfers, or deploy further malware.
Impersonation and Fraud : Users can be tricked into divulging confidential information, believing they are communicating with trustworthy sources.
Alarm Bells for Enterprises
For businesses, the ramifications of Crocodilus extend beyond personal invasion to jeopardize corporate communications and data integrity. As employees increasingly use personal devices for work, the invisible harboring of such malware could lead to unsuspected leaks of confidential information. The blend of personal and professional spheres in mobile devices heightens this risk exponentially.
Prevention and Mitigation
Security Protocols : It is imperative for organizations to enforce robust mobile security protocols. This includes deploying advanced malware protection solutions and implementing strict access controls.
User Awareness Campaigns : Educating employees about identifying suspicious activities and the vulnerabilities of their mobile devices can buffer against such threats.
Regular Updates : Encourage routine updates of applications and operating systems to patch vulnerabilities that may be exploited by Crocodilus and similar malware.
Zero Trust Approach : Adopting a Zero Trust security model can help ensure that any request for access or data transfer is rigorously verified and authenticated.
Poachers Beware: Safeguarding Your Device
While the idea of such pervasive malware might be anxiety-inducing, crooning a catchy reminder like “spot the croc before it bites” could be your best line of defense. Whether through personal diligence or organizational policies, recognizing and mitigating these threats is an ongoing battle.
Vendor Diligence Questions
1. What measures does your malware protection software take to detect and neutralize mobile threats such as Crocodilus?
2. How frequently are updates and patches released for your solutions to ensure they counteract the latest malware tactics?
3. Can you provide a demonstration or case study illustrating the efficacy of your solutions against similar mobile malware threats?
Action Plan
Mobile Policy Revision : Immediately review and update existing mobile security policies to address the specific threats posed by Crocodilus.
Team Training : Arrange workshops or seminars to educate staff on the latest mobile threats and best practices for avoiding phishing and spoofing.
IT Security Audit : Conduct an extensive mobile security audit to identify and remediate potential vulnerabilities that could be exploited by malware.
*
Source: Android malware Crocodilus adds fake contacts to spoof trusted callers
*
Account Lockout Policy: When Your Password Plays Hard to Get
_When security meets frustration, say goodbye to 3 AM password resets._
What You Need to Know
Organizations are in dire need of adopting robust account lockout policies to protect themselves against cyber threats, especially brute force attacks. Implementing a stringent lockout policy helps in reducing unauthorized access attempts, but it also has its challenges, such as user frustration and potential negative impacts on productivity. Board members and executive management should ensure that a balanced policy is implemented—one that secures the organization without driving their users bonkers.
CISO Focus: Access Management and User Authentication
Sentiment: Positive
Time to Impact: Immediate
*
Who Left the Door Open? Understanding Account Lockout Policies
Account lockout policies are becoming a pivotal part of cybersecurity strategies. They serve as automated security measures designed to protect systems from unauthorized access by limiting the number of failed login attempts. This method is crucial in deterring brute force attacks, where adversaries try to guess passwords at alarming speeds. But the challenge lies in creating policies that protect without excessively hindering the legitimate user experience.
Why Does It Matter?
* Security Enhancement: Account lockout policies are integral to safeguarding sensitive information. By preventing relentless password-guessing attacks, organizations can thwart unauthorized access.
* Risk Reduction: These policies reduce the likelihood of a hacker successfully accessing secure information systems, thus protecting the integrity of user accounts and company data.
* Compliance Adherence: Many industries must comply with regulatory standards that mandate stringent access controls, including account lockout mechanisms.
The Balancing Act
It is imperative to strike a balance when setting account lockout parameters. Here are key factors:
* Thresholds: Determine the number of unsuccessful login attempts before an account locks. Common practice suggests between three to five attempts.
* Lockout Duration: Decide for how long an account should remain locked. Options range from minutes to requiring an admin reset.
* User Experience: While a strict policy enhances security, it could also cause frustration, leading to user complaints and productivity loss.
Strategy for Success
1. Customizable Policies: Tailor policies to your organization’s specific needs and risk profile. This customization should factor in user roles and data sensitivity levels.
2. User Education: Inform users about security best practices and clearly communicate the account lockout policy to mitigate frustration.
3. Monitoring and Review: Continuously monitor account lockout reports. Analyze trends to adjust the policy and respond to genuine threats.
4. Technological Support: Implement multi-factor authentication (MFA) mechanisms to further protect accounts without solely relying on passwords.
Avoid Biting Your Lockout Line
A well-balanced lockout policy is more than just setting the rules and forgetting about them. It involves understanding the nuances of potential trade-offs between security and usability.
1. Use Leveraged Alerts: Immediate alerts for administrators on account lockout events can help in uncovering potential attack patterns or false alarms.
2. Contextual Awareness: Implement systems that distinguish between genuine login attempts from employees versus suspicious activities.
Failure's Short Fuse: When Lockout Goes Wrong
Default settings are a starting block, not the finish line. Too often, organizations use standard lockout settings without tailoring them to their unique environment, leading to potential oversights and vulnerabilities.
*
Vendor Diligence Questions
1. How does the account lockout policy integrate with existing access management systems?
2. What are the options available for customizing lockout thresholds and durations?
3. Can the system provide analytics on lockout events and adjust policies based on user behavior?
Action Plan
Review Current Policies: Evaluate existing lockout policies against industry best practices and adjust as necessary.
Role-Specific Policies: Develop lockout policies tailored to specific roles, balancing security needs with user responsibilities.
Training Initiatives: Launch a user training campaign focused on the importance of cybersecurity policies and how they impact daily operations.
Implement MFA: Work with teams to deploy multi-factor authentication measures to complement lockout policies.
*
Sources:
Account lockout policy: Setup and best practices explained. TechTarget.
CISA’s Guide to Cyber Hygiene.
NIST Digital Identity Guidelines.
*
Cryptojacking Follies: When Your DevOps Tools Go Rogue
_When GitHub turns into CryptoHub, who's left mining for answers?_
What You Need to Know
A recent exploit on DevOps APIs using off-the-shelf tools from GitHub has been uncovered. As part of a sophisticated cryptojacking campaign, cybercriminals are hijacking computing resources to mine cryptocurrency, causing operational disruptions and increased costs for organizations relying on DevOps. The exploitation underscores vulnerabilities within the DevOps ecosystem, urging immediate action on tightening security controls and diligence around tool supply chains. The executive team needs to assess the impact on their operations, ensure communications with affected stakeholders, and coordinate with the IT department to enhance security protocols.
CISO Focus: Cloud Security and DevOps Tools
Sentiment: Negative
Time to Impact: Immediate
*
Invisible Miners of DevOps
Cryptojacking—a cyber menace less visible than ransomware or data breaches, yet equally disruptive—is on the rise. A recent campaign exploits DevOps APIs, using GitHub's freely available tools to commandeer computing power across distributed environments. These attacks hijack DevOps systems' computational power to mine cryptocurrency, leading to increased operational costs and hampered system performance.
Immediate Operational Challenges
Resource Drain: The covert mining operation consumes critical computing resources, which can lead to slowed application performance and increased electricity consumption.
Security Breaches: Exploiting exposed or weakly secured DevOps APIs exposes organizations to broader security risks, potentially opening backdoors for more malicious activities.
Why GitHub?
GitHub, a kingpin of open-source collaboration, becomes a double-edged sword in this saga. Here, the same tools revered for driving innovation and efficiency are wielded with malign intent. Attackers leverage GitHub because of its accessibility and widespread adoption—a familiar landscape where DevOps professionals might inadvertently trust, leaving a gap waiting to be exploited.
Exploit Mechanics
The attackers engage in an intricate dance, intertwining novice simplicity with advanced subterfuge:
Tool Selection: They employ legitimate, off-the-shelf tools downloadable from GitHub to weave their cryptojacking magic.
Automation Scripts: These scripts automate the scanning and identification of vulnerable APIs, swiftly integrating mining operations once a viable target is detected.
Vulnerability Landscape
Infrastructure Oversights: Poorly configured DevOps infrastructures are prime targets. APIs exposed to the internet or using weak authentication mechanisms breed vulnerability.
Inadequate Monitoring: Insufficient monitoring systems fail to catch these subtle, ongoing attacks.
Tooling Trust: Reliance on third-party tools without rigorous vetting invites this form of attack, especially given the allure of widely trusted platforms like GitHub.
Tactics for Defense
1. Fortifying APIs: Regular audits and rigorous security protocols should be imposed on DevOps APIs to ensure they aren't weak links in your digital fortress.
2. Enhanced Monitoring: Implement comprehensive monitoring to detect anomalous activity patterns indicative of cryptojacking attempts.
3. Code Verification: Prioritize extensive scrutiny and verification of all third-party tools integrated into the DevOps workflow.
Mining for Conclusions
In a realm dominated by ever-evolving threats, guarding our digital citizens (APIs and DevOps tools) requires diligence and adaptability. As cryptojackers turn innovation against its creators, organizations must foster a culture of constant vigilance, proactive defenses, and utmost scrutiny of open-source dependencies.
*
Vendor Diligence Questions
1. How does the vendor ensure the security and integrity of their open-source tools against exploitation?
2. Are there mechanisms in place for rapidly identifying and patching vulnerabilities within their offerings?
3. What measures do they have to alert users to security changes or discovered vulnerabilities?
Action Plan
1. Immediate Risk Assessment: Conduct a full assessment of the organization's DevOps infrastructure and APIs to identify vulnerabilities.
2. Implement Enhanced Security Measures: Advocate for stronger security configurations within the DevOps environment, emphasizing secure API practices.
3. Increase Workforce Awareness: Conduct training to raise awareness about cryptojacking and the risks associated with open-source tools.
4. Vendor Evaluation: Initiate evaluation discussions with your third-party tool providers to ensure their security policies align with your organizational standards.
*
Source: Cryptojacking Campaign Exploits DevOps APIs Using Off-the-Shelf Tools from GitHub
*
OpenAI’s GPT-5: The New Sheriff in AI Town
_When AI dreams, reality checks itself_
What You Need to Know
The advent of OpenAI's GPT-5 is poised to redefine artificial intelligence capabilities and industry expectations. As executive leaders, it's crucial to understand the broader impacts of this leap in AI efficiency and realistic output potential, with implications across various sectors. Prepare your organization to adapt to and leverage these advancements, ensuring your team is equipped with the necessary tools and strategies to remain competitive in this swiftly evolving landscape.
CISO Focus: Artificial Intelligence Advancements
Sentiment: Strong Positive
Time to Impact: Immediate
*
OpenAI’s GPT-5: Ushering in AI's Golden Era
In a definitive stride towards more advanced artificial intelligence, OpenAI’s highly anticipated next iteration—GPT-5—is setting the technological world abuzz. With its release just on the horizon, GPT-5 is poised not merely to compete but to potentially overshadow its predecessors with unprecedented capabilities in understanding and generating human-like text. Joe Montana, the brainchild behind OpenAI's innovation, heralds this as a milestone that bridges the chasm between human creativity and machine logic.
Key Features and Enhancements
OpenAI's GPT-5 brings with it a significant expansion in both operational competencies and intricacies, underscoring the evolutionary leap from GPT-4. Among the headline features:
Enhanced Contextual Understanding: With a more than doubled parameter count, GPT-5 elevates its contextual comprehension, enabling it to grasp nuanced language and complex instructions with greater accuracy, thus greatly improving its conversational AI capabilities.
Reduction in LLM Hallucinations: A marked advancement is its higher precision in reducing incorrect or fabricated responses—a bane in the AI realm—reinforcing trustworthiness and reliability in generated content.
Scalability and Cost-effectiveness: New architectural refinements mean GPT-5 can run more efficiently, potentially lowering costs for enterprises looking to integrate AI solutions at scale across digital platforms.
Industry Applications
The unveiling of GPT-5 is set to ripple across multiple sectors, revolutionizing workflows, enhancing customer experiences, and inspiring innovative applications. In sectors such as healthcare, finance, and education, AI applications will benefit from GPT-5's sophisticated learning capabilities, providing more accurate data analysis and decision-making frameworks.
For example, in healthcare, GPT-5’s advanced language processing could significantly improve diagnostic processes and patient interaction models. In finance, its predictive prowess and analytical capabilities could elevate risk management and investment strategies to new levels.
The Competitive Edge
As enterprises gear towards digital transformation, integrating GPT-5 can provide a substantial competitive advantage. Organizations must recognize the significance of adopting AI to harness smarter automation, deliver tailored customer experiences, and foster innovative product development. Importantly, staying at the forefront of AI development ensures longevity in a tech-centric market environment.
OpenAI's strategic collaborations with key industry players signal a burgeoning ecosystem, where business and AI symbiosis are not just ideal but imperative. By fostering partnerships, OpenAI aims to make AI tools ubiquitous, eliminating barriers and democratizing technology as an accessible resource for all industries.
Thoughtful Implementation and Ethical Considerations
Despite the promising prospects, deploying GPT-5 requires careful implementation to mitigate risks associated with AI, such as ethical dilemmas and bias. Ethical AI use remains a priority, demanding businesses to uphold transparency, fairness, and accountability.
Companies should proactively engage with ethical guidelines, aligning AI applications with societal values while ensuring compliance with international AI regulations and standards. This approach will safeguard businesses against potential reputational damage and foster trust with customers and stakeholders.
What’s Next in the AI Odyssey?
The era of OpenAI's GPT-5 is set to revolutionize AI narratives, inviting debate and discourse on control, creativity, and commerce. To navigating this burgeoning landscape demands strategic foresight, adaptability, and above all, a commitment to responsible AI innovation.
As Echoes of Evolution flutter through the digital fabric, GPT-5 might just be playing the maestro in AI's symphony, orchestrating a harmonious blend of machine precision with the spontaneity of human thought.
*
Vendor Diligence Questions
1. What proprietary technologies or methodologies distinguish your AI solutions from those using GPT-4?
2. How does your company handle the ethical challenges associated with AI use, particularly regarding data privacy and bias mitigation?
3. Can you provide case studies or testimonials showcasing the integration success of GPT-5 in specific industry applications?
Action Plan
Assessment: Evaluate current workflows where GPT-5's capabilities can be leveraged for enhanced efficiencies.
Training: Initiate training sessions for employees to understand the utilization of GPT-5 in relevant domains.
Integration: Collaborate with IT and data science teams to integrate GPT-5 into existing systems, ensuring alignment with business goals.
Compliance: Review and update organizational AI and data policies to align with ethical standards and relevant international regulations.
*
Source: OpenAI is hopeful GPT-5 will compete a little more
The Crown Jewel of Certificates: Chrome’s No-Show for Misbehaving Authorities
_In the land of digital trust, there’s new residency criteria: Don’t get caught._
What You Need to Know
What you need to know is that Google Chrome will soon stop trusting digital certificates from two certificate authorities, TrustCor Systems and another non-disclosed entity, due to their non-compliance with industry standards and behavioral conduct concerns. This distrust impacts organizations with certificates issued by these authorities, prompting them to switch to other trusted providers. Executive management must prioritize this swiftly to protect their organization’s web presence and reputation.
CISO Focus: Web Security and Compliance
Sentiment: Negative
Time to Impact: Immediate
*
In a move as surprising as your toddler cracking the family iPad’s password, Google Chrome has announced a decision to distrust certificates from TrustCor Systems and one other, mysterious certificate authority due to significant compliance and conduct violations. This pivot affects countless digital certificates globally, demanding immediate attention from organizations as their online authenticity hangs in the balance.
What Happened?
Google's security team discovered that TrustCor Systems and another certificate authority were involved in activities inconsistent with the best practices defined by the CA/B Forum—a coalition of browsers and certificate authorities that sets guidelines for certificates. Violations include inadequate auditing of certificates and participation in questionable partnerships, which raised red flags about their adherence to transparency and ethical standards.
This distrust means that web resources depending on certificates from these authorities will be flagged as unsafe by Google Chrome, leading to potential user loss, damage to brand reputation, and possibly, decreased revenue. Companies reliant on these certificates find themselves needing to switch certificate providers, effectively ponouncing the R-key mistake in "redeploy" with urgency.
The Scope of the Issue
Immediate Effects: Websites using certificates from the dismissed authorities will start displaying warning messages in Chrome, essentially branding them unsafe. This could lead to reduced website traffic and credibility issues.
Customer Trust: Digital certificates are the backbone of online security—data exchanged across the internet relies on these digital identifiers for encryption. While changing certificate providers will restore trust, organizations face the uphill task of regaining any potential loss of customer faith.
Broader Implications
The incident not only impacts those directly affected but sounds alarm bells across the digital world about the precariousness of the current digital certificate landscape. With critical infrastructures relying more heavily on encrypted communications, the incident raises demands for stricter adherence and independent audits in practices by all Certificate Authorities (CAs).
Organizations may also re-evaluate their digital security strategies, perhaps shifting towards automated management solutions to avoid reliance on a single CA provider. However, this requires careful planning and resources to transition smoothly without service interruptions.
In the Browser Wars
This move by Google is consistent with its aggressive push towards security, but it also places unprecedented pressure on trusts and certifying authorities to maintain high standards of performance and ethics. As other browsers might follow in Chrome's decisive steps, the digital security community watches closely to gauge if this will evolve into an industry-wide purging of inadequate players.
*
Vendor Diligence Questions
1. Has your Certificate Authority conducted recent independent audits, and can they provide transparent reports?
2. How does your vendor ensure compliance with the CA/B Forum's guidelines, and what measures are in place to prevent misconduct?
3. Can they assure continuity and reliability in case of re-distrust or compliance issues by a major browser?
Action Plan
Identify and Prioritize: All affected digital certificates issued by TrustCor Systems or any related certificate authority should be identified and prioritized based on criticality.
Seek Alternatives: Quickly engage alternative Certificate Authorities vetted for adherence to guidelines.
Monitor and Report: Regularly monitor the transition process and provide updates to the executive team, ensuring all parties are informed.
Engage with Browser Vendors: Consider informing other browsers about your current situation to ensure support and a smoother transition.
Notify Stakeholders: Communicate transparently with stakeholders, including users, about the steps taken to rectify the issue to maintain transparency and trust.
*
Sources:
"Google Chrome to Stop Trusting Two Certificate Authorities," The Hacker News. Source URL
Internet Security Research Group (ISRG)
Certificate Authority/Browser (CA/B) Forum
*
The Devil Wears Command Lines: Backdoors in Python and NPM Packages
_You know things are bad when programming tools need virus warnings more than grandpa's old PC._
What You Need to Know
The recent discovery by Checkmarx Zero of malicious software infiltrating Python and NPM packages requires urgent board level attention. The attack uses typosquatting to trick developers into downloading backdoor-laden software. This risks the integrity of both Windows and Linux systems. Executive management should ensure immediate evaluation of software dependencies and should mandate a review of current supply chain security practices.
CISO focus: Supply Chain Security, Code Integrity
Sentiment: Strong Negative
Time to Impact: Immediate
*
The simmering issue of software supply chain vulnerabilities has erupted into a full-blown crisis with the latest revelation from Checkmarx Zero. This insidious campaign preys on unwary developers by embedding backdoors in Python and NPM packages, contaminating systems running Windows and Linux alike.
A Cross-Platform Menace
At the heart of the campaign is a clever misuse of typosquatting—a technique familiar to anyone who's ever mistyped a URL and ended up in the internet's less savory neighborhoods. Malicious actors are employing names that closely mimic popular software tools, like 'colorama' and 'colorizr', but with a cross-boundary audacity: using a Python name in an NPM package and vice versa. This sleight of hand parallels hitching a ride on the Uber to a destination no one would willingly choose.
The Technical Aspects
These backdoors, found in packages uploaded on Python Package Index (PyPI), cleverly masquerade as legitimate dependencies. Upon incorporation into development environments, they can execute arbitrary code. The potential implications are severe, including data breaches, intellectual property theft, and the compromise of sensitive customer information.
Attack Vector : Typosquatting on PyPI and NPM
Worthless Doppelgängers : Legit-sounding, but malicious, twins of popular code
Systems At Risk : Both Windows and Linux environments are vulnerable
Broader Implications
The involvement of mainstream tools marks a worrying trend toward more aggressive and widespread software supply chain attacks. This campaign has uncovered a glaring vulnerability not just in developer vigilance but in the infrastructure that supports some of the most critical elements of modern software development.
"In a world where time is our most important asset, wasting it dealing with preventable security breaches is akin to burning money," explains cyber strategist, Alex Montoya.
The Developer's Dilemma
For developers, who often juggle tight deadlines with demanding feature lists, the allure of easily accessible external code is hard to resist. However, this incident highlights the urgent need for developers and organizations alike to integrate more robust vetting processes into their operations.
Best Practices
Enhance scrutiny of package origins.
Implement a robust code-review process.
Educate developers on supply chain security.
The Call for Enhanced Regulation
Perhaps the most worrisome aspect of these attacks lies in the apparent ease with which malicious actors can exploit existing ecosystems, underscoring the need for more stringent checks and balances across platforms. Cybersecurity expert James T. Holbrook emphasizes, "Regulation might feel like a thorn in the flesh for industry creatives, but without it, we're inviting wolves into the fold."
Wrapping it Up... like a Trojan Horse
In an unforgiving cyber landscape, this episode serves as another stark reminder of the vulnerabilities inherent in modern software development. Organizations must be proactive, not reactive, incorporating security at every level from day one. Failing to do so risks not only operational integrity but the trust and safety of those they serve.
*
Vendor Diligence Questions
1. How does your solution ensure the integrity and authenticity of third-party packages?
2. Can you provide documentation on your process for identifying and addressing vulnerabilities in external dependencies?
3. What proactive measures do you have in place for preemptively identifying typosquatting attacks?
Action Plan
1. Immediate Review: Conduct an audit of all external packages used in development projects; prioritize those sourced from PyPI and NPM.
2. Security Integration: Fast-track the implementation of Application Security Testing (AST) tools that can identify and block malicious packages.
3. Training & Awareness: Organize workshops for developers focusing on best practices for package management and the importance of software supply chain security.
*
Sources:
[HackRead](https://hackread.com/backdoors-python-npm-packages-windows-linux/)
[Checkmarx Zero Study](https://checkmarx.com/zero-post/python-pypi-supply-chain-attack-colorama)
Alex Montoya's commentary on supply chain vulnerabilities
*
_CISO Intelligence is lovingly curated from open source intelligence newsfeeds and is aimed at helping cybersecurity professionals be better, no matter what their stage in their career._
_We’re a small startup, and your subscription and recommendation to others is really important to us._
*Thank you so much for your support!(