Critical Zero Trust Implementation Blunders Companies Must Avoid Now

 

Introduction: The Urgent Mandate of Zero Trust

In an era of dissolved perimeters and sophisticated threats, the traditional “trust but verify” security model is obsolete. The rise of distributed workforces and complex cloud environments has rendered castle-and-moat defenses ineffective, making a new mandate clear: Zero Trust. This security framework operates on a simple yet powerful principle: never trust, always verify. It assumes that threats can originate from anywhere, both inside and outside the network, and demands that no user or device be granted access until their identity and context are rigorously validated.

ZeroTrustScorecard

The Shifting Security Perimeter: Why Zero Trust is Non-Negotiable

The modern enterprise no longer has a single, defensible perimeter. Data and applications are scattered across on-premises data centers, multiple cloud platforms, and countless endpoints. This new reality is a goldmine for attackers, who exploit implicit trust within networks to move laterally and escalate privileges. This is compounded by the challenges of remote work; research from Chanty shows that 76% of cybersecurity professionals believe their organization is more vulnerable to cyberattacks because of it. A Zero Trust security model directly confronts this reality by treating every access request as a potential threat, enforcing strict identity verification and least-privilege access for every user and device, regardless of location.

The High Stakes of Implementation: Why Avoiding Blunders is Critical

Adopting a Zero Trust framework is not a minor adjustment—it is a fundamental transformation of an organization’s security posture. While the benefits are immense, the path to implementation is fraught with potential pitfalls. A misstep can do more than just delay progress; it can create new security gaps, disrupt business operations, and waste significant investment. Getting it right requires a strategic, holistic approach. Understanding the most common and critical implementation blunders is the first step toward building a resilient and effective Zero Trust architecture that truly protects an organization’s most valuable assets.

Blunder 1: Mistaking Zero Trust for a Product, Not a Strategy

One of the most pervasive and damaging misconceptions is viewing Zero Trust as a single technology or a suite of products that can be purchased and deployed. This fundamentally misunderstands its nature and sets the stage for inevitable failure.

The Product Pitfall: Believing a Single Solution Solves All

Many vendors market their solutions as “Zero Trust in a box,” leading organizations to believe that buying a specific firewall, identity management tool, or endpoint agent will achieve a Zero Trust posture. This product-centric view ignores the interconnectedness of users, devices, applications, and data. No single vendor or tool can address the full spectrum of a Zero Trust architecture. This approach often results in a collection of siloed security tools that fail to communicate, leaving critical gaps in visibility and enforcement.

The Strategic Imperative: Developing a Comprehensive Zero Trust Vision

True Zero Trust is a strategic framework and a security philosophy that must be woven into the fabric of the organization. It requires a comprehensive vision that aligns security policies with business objectives. This Zero Trust strategy must define how the organization will manage identity, secure devices, control access to applications and networks, and protect data. It is an ongoing process of continuous verification and refinement, not a one-time project with a clear finish line.

Avoiding the Trap: Actionable Steps for a Strategic Foundation

To avoid this blunder, organizations must begin with strategy, not technology. Form a cross-functional team including IT, security, networking, and business leaders to develop a phased roadmap. This plan should start by defining the most critical assets and data to protect—the “protect surface.” From there, map transaction flows, architect a Zero Trust environment, and create dynamic security policies. This strategic foundation ensures that technology purchases serve the overarching goals, rather than dictating them.

Blunder 2: Skipping Comprehensive Inventory and Underestimating Scope

A core principle of Zero Trust is that you cannot protect what you do not know exists. Many implementation efforts falter because they are built on an incomplete or inaccurate understanding of the IT environment. Diving into policy creation without a complete asset inventory is like trying to secure a building without knowing how many doors and windows it has.

The “Unknown Unknowns”: Securing What You Don’t See

Organizations often have significant blind spots in their IT landscape. Shadow IT, forgotten legacy systems, unmanaged devices, and transient cloud workloads create a vast and often invisible attack surface. Without a comprehensive inventory of all assets—including users, devices, applications, networks, and data—it’s impossible to apply consistent security policies. Attackers thrive on these “unknown unknowns,” using them as entry points to bypass security controls.

The Scope Illusion: Underestimating All Connected Workloads and Cloud Environments

The scope of a modern enterprise network extends far beyond the traditional office. It encompasses multi-cloud environments, SaaS applications, IoT devices, and API-driven workloads. Underestimating this complexity is a common mistake. A Zero Trust strategy must account for every interconnected component. Failing to discover and map dependencies between these workloads can lead to policies that either break critical business processes or leave significant security vulnerabilities open for exploitation.

Avoiding the Trap: The Foundational Importance of Discovery and Continuous Asset Management

The solution is to make comprehensive discovery and inventory the non-negotiable first step. Implement automated tools that can continuously scan the environment to identify and classify every asset. This is not a one-time task; it must be an ongoing process of asset management. This complete and dynamic inventory serves as the foundational data source for building effective network segmentation, crafting granular access control policies, and ensuring the Zero Trust architecture covers the entire digital estate.

Blunder 3: Neglecting Network Segmentation and Micro-segmentation

For decades, many organizations have operated on flat, highly permissive internal networks. Once an attacker breaches the perimeter, they can often move laterally with ease. Zero Trust dismantles this outdated model by assuming a breach is inevitable and focusing on containing its impact through rigorous network segmentation.

The Flat Network Fallacy: A Breadth-First Attack Vector

A flat network is an attacker’s playground. After gaining an initial foothold—often through a single compromised device or set of credentials—they can scan the network, discover valuable assets, and escalate privileges without encountering significant barriers. This architectural flaw is responsible for turning minor security incidents into catastrophic data breaches. Relying on perimeter defense alone is a failed strategy in the modern threat landscape.

The Power of Micro-segmentation: Isolating Critical Assets

Micro-segmentation is a core tenet of Zero Trust architecture. It involves dividing the network into small, isolated zones—sometimes down to the individual workload level—and enforcing strict access control policies between them. If one workload is compromised, the breach is contained within its micro-segment, preventing the threat from spreading across the network. This granular control dramatically shrinks the attack surface and limits the blast radius of any security incident.

Avoiding the Trap: Designing Granular Access Controls

To implement micro-segmentation effectively, organizations must move beyond legacy VLANs and firewall rules. Utilize modern software-defined networking and identity-based segmentation tools to create dynamic security policies. These policies should enforce the principle of least privilege, ensuring that applications, workloads, and devices can only communicate with the specific resources they absolutely require to function. This approach creates a resilient network where lateral movement is difficult, if not impossible.

Blunder 4: Overlooking Identity and Access Management Essentials

In a Zero Trust framework, identity is the new perimeter. Since trust is no longer granted based on network location, the ability to robustly authenticate and authorize every user and device becomes the cornerstone of security. Failing to fortify identity management practices is a fatal flaw in any Zero Trust initiative.

The Weakest Link: Compromised Credentials and Privileged Accounts

Stolen credentials remain a primary vector for major data breaches. Weak passwords, shared accounts, and poorly managed privileged access create easy pathways for attackers. An effective identity management program is essential for mitigating these risks. Without strong authentication mechanisms and strict controls over privileged accounts, an organization’s Zero Trust ambitions will be built on a foundation of sand.

The Static Access Mistake: Assuming Trust After Initial Authentication

A common mistake is treating authentication as a one-time event at the point of login. This “authenticate once, trust forever” model is antithetical to Zero Trust. A user’s context can change rapidly: they might switch to an unsecure network, their device could become compromised, or their behavior might suddenly deviate from the norm. Static trust models fail to account for this dynamic risk, leaving a window of opportunity for attackers who have hijacked an active session.

Avoiding the Trap: Fortifying Identity Security Solutions

A robust Zero Trust strategy requires a mature identity and access management (IAM) program. This includes enforcing strong, phishing-resistant multi-factor authentication (MFA) for all users, implementing a least-privilege access model, and using privileged access management (PAM) solutions to secure administrative accounts. Furthermore, organizations must move toward continuous, risk-based authentication, where access is constantly re-evaluated based on real-time signals like device posture, location, and user behavior.

Blunder 5: Ignoring Third-Party Access and Supply Chain Risks

An organization’s security posture is only as strong as its weakest link, which often lies outside its direct control. Vendors, partners, and contractors are an integral part of modern business operations, but they also represent a significant and often overlooked attack vector.

The Extended Attack Surface: Vendor and Supply Chain Vulnerabilities

Every third-party vendor with access to your network or data extends your attack surface. These external entities may not adhere to the same security standards, making them prime targets for attackers seeking a backdoor into your organization. In fact, a staggering 77% of all security breaches originated with a vendor or other third party, according to a Whistic report. Ignoring this risk is a critical oversight.

Lax Access Control for External Entities: A Gateway for Attackers

Granting vendors broad, persistent access—often through traditional VPNs—is a recipe for disaster. This approach provides them with the same level of implicit trust as an internal employee, allowing them to potentially access sensitive systems and data far beyond the scope of their legitimate needs. If a vendor’s network is compromised, that access becomes a direct conduit for an attacker into your environment.

Avoiding the Trap: Strict Vetting and Granular Controls

Applying Zero Trust principles to third-party access is non-negotiable. Begin by conducting rigorous security assessments of all vendors before granting them access. Replace broad VPN access with granular, application-specific access controls that enforce the principle of least privilege. Each external user’s identity should be strictly verified, and their access should be limited to only the specific resources required for their role, for the minimum time necessary.

Blunder 6: Disregarding User Experience and Neglecting Security Awareness

A Zero Trust implementation can be technically perfect but fail completely if it ignores the human element. Security measures that are overly complex or disruptive to workflows will inevitably be circumvented by users focused on productivity.

The Friction Fallout: User Workarounds and Shadow IT Resurgence

If security policies introduce excessive friction—such as constant, unnecessary authentication prompts or blocked access to legitimate tools—employees will find ways around them. This can lead to a resurgence of Shadow IT, where users adopt unsanctioned applications and services to get their work done, creating massive security blind spots. A successful Zero Trust strategy must balance security with usability.

The Human Firewall Failure: Lack of Security Awareness Training

Zero Trust is a technical framework, but it relies on users to be vigilant partners in security. Without proper training, employees may not understand their role in the new model. They may fall for sophisticated phishing attacks, which have seen a 1,265% increase driven by GenAI, unknowingly providing attackers with the initial credentials needed to challenge the Zero Trust defenses.

Avoiding the Trap: Empowering Users with Secure Simplicity

Strive to make the secure path the easy path. Implement solutions that leverage risk-based, adaptive authentication to minimize friction for low-risk activities while stepping up verification for sensitive actions. Invest in continuous security awareness training that educates employees on new threats and their responsibilities within the Zero Trust framework. When users understand the “why” behind the security policies and find them easy to follow, they become a powerful asset rather than a liability.

Blunder 7: Treating Zero Trust as a “Set It and Forget It” Initiative

The final critical blunder is viewing Zero Trust as a project with a defined endpoint. The threat landscape, technology stacks, and business needs are in a constant state of flux. A Zero Trust architecture that is not designed to adapt will quickly become obsolete and ineffective.

The Static Security Stagnation: Failing to Adapt to Threat Landscape Changes

Attackers are constantly evolving their tactics. A security policy that is effective today may be easily bypassed tomorrow. A static Zero Trust implementation fails to account for this dynamic reality. Without continuous monitoring, analysis, and refinement, security policies can become stale, and new vulnerabilities in applications or workloads can go unnoticed, creating fresh gaps for exploitation. Furthermore, the integration of automation is crucial, as organizations using security AI can identify and contain a data breach 80 days faster than those without.

Conclusion

Successfully implementing a Zero Trust architecture is a transformative journey that demands strategic foresight and meticulous execution. The path is challenging, but by avoiding these critical blunders, organizations can build a resilient, adaptive security posture fit for the modern digital era.

The key takeaways are clear:

  • Embrace the Strategy: Treat Zero Trust as a guiding philosophy, not a checklist of products. Build a comprehensive roadmap before investing in technology.
  • Know Your Terrain: Make complete and continuous inventory of all assets—users, devices, workloads, and data—the absolute foundation of your initiative.
  • Isolate and Contain: Leverage micro-segmentation to shrink your attack surface and prevent the lateral movement of threats.
  • Fortify Identity: Make strong, adaptive identity and access management the core of your security controls.
  • Balance Security and Usability: Design a framework that empowers users and integrates seamlessly into their workflows, supported by ongoing security awareness.
  • Commit to the Journey: Recognize that Zero Trust is an iterative, ongoing process of refinement and adaptation, not a one-time project.

By proactively addressing these potential pitfalls, your organization can move beyond legacy security models and chart a confident course toward a future where trust is never assumed and every single access request is rigorously verified.

Contact MicroSolved, Inc. for More Information or Assistance

For expert guidance on implementing a resilient Zero Trust architecture tailored to your organization’s unique needs, consider reaching out to the experienced team at MicroSolved, Inc. With decades of experience in information security and a proven track record of helping companies navigate complex security landscapes, MicroSolved, Inc. offers valuable insights and solutions to enhance your security posture.

  • Phone: Reach us at +1.614.351.1237
  • Email: Drop us a line at info@microsolved.com
  • Website: Visit our website at www.microsolved.com for more information on our services and expertise.

Our team of seasoned experts is ready to assist you at any stage of your Zero Trust journey, from initial strategy development to continuous monitoring and refinement. Don’t hesitate to contact us for comprehensive security solutions that align with your business goals and operational requirements.

 

 

* AI tools were used as a research assistant for this content, but human moderation and writing are also included. The included images are AI-generated.

 

 

5 Fun-tastic Fall Activities for Information Security Teams

 

Fall is in the air, and along with pumpkin spice lattes and cozy sweaters, it’s also the perfect time for information security teams to step out of their digital shells and engage with other departments in their organizations. While security is serious business, there’s no harm in adding a dash of fun to foster better collaboration and understanding. Here are five light-hearted yet factual activities to spice up your information security team’s fall:

1. Cybersecurity Pumpkin Carving Contest

Unleash your inner artist and host a cybersecurity-themed pumpkin carving contest. Encourage teams from all departments to carve out their favorite security tools, icons, or even infamous cyber villains. Not only does this activity tap into everyone’s creative side, but it also sparks conversations about the importance of protecting the digital realm while having a gourd time!

2. “Escape the Phishing” Maze

Turn the concept of an escape room into an interactive cybersecurity challenge. Create a “phishing” maze where participants need to navigate through a series of puzzles and scenarios related to online security. This activity not only educates participants about the dangers of phishing attacks but also gets them working together to solve problems, fostering team spirit.

3. Crypto Treasure Hunt

Transform your office space into a treasure hunting ground by organizing a crypto-themed treasure hunt. Provide clues related to encryption, decryption, and security best practices that lead teams from one clue to another. Not only does this activity promote learning about cryptography, but it also encourages friendly competition among departments.

4. Security Awareness Fair

Set up a “Security Awareness Fair” in your office’s common area. Each department can have its own booth showcasing their approach to security. From IT’s “Spot the Vulnerability” game to HR’s “Password Strength Analyzer,” everyone gets to display their security prowess in a fun and informative way. This fair promotes cross-departmental engagement and ensures that everyone learns a thing or two about cybersecurity.

5. Cyber Movie Night

Host a cybersecurity-themed movie night with popcorn and cozy blankets. Screen movies like “Hackers,” “WarGames,” or even cybersecurity documentaries. After the movie, encourage lively discussions about what’s accurate and what’s exaggerated in the portrayal of hacking and security. It’s a laid-back way to bridge the gap between tech-savvy and non-technical teams.

Remember, the goal of these activities isn’t just to have fun, but to build bridges between information security teams and other departments. By approaching cybersecurity engagement with a light-hearted touch, you’re more likely to break down barriers, share knowledge, and create a culture of collaboration that lasts beyond the fall season. So, gear up for a season of learning, laughter, and interdepartmental camaraderie!

 

* Just to let you know, we used some AI tools to gather the information for this article, and we polished it up with Grammarly to make sure it reads just right!

 

New Book Launch: We Need To Talk: 52 Weeks To Better Cyber-Security

I have released a new e-book titled “We Need To Talk: 52 Weeks To Better Cyber-Security.” I self-published through PublishDrive and MSI. It has been quite an interesting project, and I learned a lot in both writing/editing (with an AI), and in the publishing aspects.

The book provides a comprehensive approach to discussing cyber-security, addressing topics such as risk management, configuration management, vulnerability management, policy, threat intelligence, and incident response. The discussions that are sparked will lead to helping your team strengthen and mature your organization’s security posture.

The book is designed for information security professionals and their teams looking for a structured way to improve their organization’s cyber-security posture over one year. It is an ideal resource for those teams who wish to develop a well-rounded understanding of cyber-security and gain insight into the various elements that are needed for a successful program.

The book is 111 pages and sells for $9.99 in most of the ebook stores below:

Amazon

Apple

Barnes & Noble

Check it out, and please leave a review if you don’t mind taking the time. It will be much appreciated.

Print-on-demand options and other stores will be coming shortly. Hopefully, the book helps folks build better infosec programs. As always, thanks for reading, and stay safe out there! 

Supply Chain Security Insights

Supply chain attacks are one of the most common cyber threats faced by organizations. They are costly and disruptive, often resulting in lost revenue and customer trust.

In this article, we’ll discuss five insights about supply chain attacks that all supply chain management and information security teams should be aware of.

#1. Supply Chains Can Be Vulnerable

Supply chains are complex networks of companies, suppliers, customers, and partners that provide goods and services to each other.

They include manufacturers, distributors, retailers, service providers, logistics providers, and others.

These entities may interact directly or indirectly via intermediaries such as banks, insurance companies, payment processors, freight forwarders, customs brokers, etc.

Supply chains are vulnerable to attack because they involve multiple parties and interactions between them. Each organization in the chain will have its own risk profile, security posture, and business model. This creates a complex environment for security risks. Attackers can target any part of the supply chain, and often focus on the weakest link, including manufacturing facilities, distribution centers, warehouses, transportation hubs, retail stores, etc.

Attackers can disrupt operations, steal intellectual property, damage reputation, and cause losses in revenue and profits.

#2. Supply Chain Security Must Include All Stakeholders

Supply chain security involves protecting against threats across the entire value stream. This means securing data, processes, systems, physical assets, personnel, and technology.

It also requires integrating security practices and technologies across the entire organization.

This includes ensuring that information sharing occurs among stakeholders, that employees understand their roles and responsibilities, and that policies and procedures are followed.

Security professionals should collaborate closely with executives, managers, and staff members to ensure that everyone understands the importance of security and has ownership over its implementation.

#3. Supply Chain Security Requires Ongoing Monitoring and Maintenance

Supply chain security requires ongoing monitoring and maintenance.

An effective approach is to continuously monitor the status of key indicators, assess risks, identify vulnerabilities, and implement countermeasures.

For example, an attacker could attempt to compromise sensitive data stored in databases, websites, mobile apps, and other locations.

To prevent these incidents, security teams should regularly review logs, audit reports, and other intelligence sources to detect suspicious activity.

They should also perform penetration tests, vulnerability scans, and other assessments to uncover potential weaknesses.

#4. Supply Chain Security Requires Collaboration Across Organizations

A single department cannot manage supply chain security within an organization.

Instead, it requires collaboration across departments and functional areas, including IT, finance, procurement, human resources, legal, marketing, sales, and others.

Each stakeholder must be responsible for maintaining security, understanding what constitutes acceptable behavior, and implementing appropriate controls.

Collaborating across organizational boundaries helps avoid silos of knowledge and expertise that can lead to gaps in security awareness and training.

#5. Supply Chain Security Is Critical to Organizational Success

Organizations that fail to protect their supply chains face significant financial penalties.

A recent study found that supply chain breaches cost United States businesses $6 trillion annually.

That’s equivalent to nearly 10% of the annual global GDP.

Supply chain attacks can result in lost revenues, damaged reputations, and increased costs.

Companies that invest in supply chain security can significantly improve operational efficiency, productivity, profitability, and brand image.

How to Rotate Your SSH Keys

SSH keys are used to secure access to and authenticate authorized users to remote servers. They are stored locally on the client machine and are encrypted using public-key cryptography. These keys are used to encrypt communications between the client and server and provide secure remote access.

When you log into a remote machine, you must provide a valid private key to decrypt the traffic. As long as the private key remains secret, only you can access the server. However, if someone obtains your private key, they can impersonate you on the network.

SSH key rotation helps prevent this type of unauthorized access. It reduces the risk that someone has access to your private key, and helps prevent malicious users from being able to impersonate you on your network.

Most security policies and best practices call for rotating your key files on a periodic basis, ranging from yearly to quarterly, depending on the sensitivity of the data on the system. Such policies go a long way to ensuring the security of authentication credentials and the authentication process for sensitive machines.

There are two ways to rotate your keys: manually, and automatically.

Manually

To manually perform key rotation, you need to generate a new pair of keys. Each time you do this, you create a new key pair. You then upload the public key file to the server you wish to connect to. Once uploaded, the server uses the public key to verify that you are who you say you are.

Automatically

An alternative approach is to use automatic key rotation. With automatic rotation, you don’t need to generate a new key pair each time you change your password. Instead, you simply update the permissions on your existing key file.

The following steps show how to configure automatic rotation.

1. Generate a new keypair

2. Upload the public key to the remote server

3. Configure the remote server to use the new keypair

4. Update the permissions on the old keypair file

5. Delete the old keypair

6. Logout from the remote server

More Information

On Linux systems, use the “man” command to learn more about the following:

    • ssh-keygen command
    • ssh-public-key command
    • upload-ssh-public-key command

The examples should provide options for command parameters and sample command output for your operating system.

For more information about the SSH protocol, you can review the Wikipedia article here.

 

Four Uses for the Raspberry Pi in Small Business Security

With Raspberry Pi systems now available fully decked out for under $100, there are many uses that small business security teams can find for these versatile devices. Here are four of our favorites for using them in security roles.

1. Honeypot for Detecting Attackers on Your Network

Our HoneyPoint™ Agent runs on the Pi. It allows you to monitor for potential network compromises and attempts to breach your network by offering a fake system for attackers to target. Since the system has no real use, any interaction with it is suspicious at best, and malicious at worst. This allows for an easy-to-manage detection tool for your business.

2. Nessus Scanning Engine for Vulnerability Management

Nessus now supports running on the Pi 4 with 8 Gigs of RAM. Nessus is a very popular and powerful vulnerability scanner. With it, you can scan your network for vulnerabilities and find out what software needs updating.

3. Run Pi-Hole for Content Filtering

Pi-Hole is one of the best open-source security tools on the Internet. It provides enterprise-quality content filtering for free. Drop this on your network and implement it following the online instructions, and you’ve got affordable protection against malicious advertising, bad content, and many types of malware that inject via the browser.

4. Build a Cheap VPN Server

PiVPN makes setting a VPN for your small business needs incredibly simple. You can use this feature to access systems while you’re away or just to stay safer on public wireless networks. Most folks can deploy this in under an hour, and it can save you an immense amount of risk.

Using a Pi for some other risk management or security purpose? We’d love to hear about it. Drop me a line on Twitter (@lbhuston) and let me know what you’re up to. We’ll feature any ground breaking ideas in future posts.

 

3 Essential Raspberry Pi Hardening Steps

Raspberry Pi hardening is essential for securing your device against attacks.

Here are three essential Raspberry Pi hardening steps:

1. Disable SSH If You Don’t Need It

Disable SSH access to your Raspberry Pi using the following command:

sudo raspi-config

Choose “Advanced Options” and then choose “No ssh”.

2. Change Your Password

Change your password to something secure. You can use the following command:

passwd

3. Update Raspbian

Update your Raspberry Pi’s operating system to the latest version available. This ensures that your device is up to date with security patches and bug fixes.

To update your Raspberry Pi, follow these instructions:

sudo apt-get update

sudo apt-get upgrade

In summary, hardening your device by following these steps will help you protect your Pi from attacks. Making these three basic steps a part of every Pi install you do will go a long way to giving you a safer, more dependable, and more private experience.

 

 

Saved By Ransomware Presentation Now Available

I recently spoke at ISSA Charlotte, and had a great crowd via Zoom. 

Here is the presentation deck and MP3 of the event. In it, I shared a story about an incident I worked around the start of Covid, where a client was literally saved from significant data breach and lateral spread from a simple compromise. What saved them, you might ask? Ransomware. 

That’s right. In this case, ransomware rescued the customer organization from significant damage and a potential loss of human life. 

Check out the story. I think you’ll find it very interesting. 

Let me know if you have questions – hit me up the social networks as @lbhuston.

Thanks for reading and listening! 

Deck: https://media.microsolved.com/SavedByRansomware.pdf

MP3: https://media.microsolved.com/SavedByRansomware.mp3

PS – I miss telling you folks stories, in person, so I hope you enjoy this virtual format as much as I did creating it! 

After Nearly 30 Years in CyberSecurity, I Still Learn Something Every Day

Cybersecurity Playtime Today:

Today, while searching through some web logs and reviewing some of the data from our HoneyPoint deployments, I found an interesting scan. The payload was pretty common, something we see, nearly every day – but the source, a pretty mature organization with a reputation for being tightly managed and capable, was what caught my eye. The scans went on for several days across a couple of weeks – sourced from a web server that clearly was not as securely managed as their reputation might insist. So, I notified them, of course, and played in the data a while, fascinated by some of the nuances of it. 

Good Days Versus Bad Days:

This is pretty much a daily occurrence for me – on the good days, at least. I get to play with data, learn something new, experiment, hypothesize and test myself. Those are the good days of being an infosec entrepreneur, CEO and researcher. The bad days are the ones when I have to struggle with sales efforts, manage difficult resources/projects or solve the same security problems as I tackled in the 90s. Those are the days when I am less happy about what I do. But, fortunately, those days are pretty few and far between. 

Fighting the Cybersecurity Good Fight:

After 30+ years in technology and “cybersecurity”, I still find a wealth of things to learn and play with. I never seem to get to the point where I feel like I know stuff. I try and remain intellectually curious and mentally humble at all times. I also try to believe in the magic of technology and fight the cynicism of doing infosec for 30 years. That keeps me making new things, and investing in new solutions, like our new ClawBack data leak detection tool

I try to keep fighting the good fight, so to speak. I’ve spent a lot of time learning about attackers – what motivates them, how they operate and how tools evolve. I’ve learned a lot about the economics of cyber-crime and the information security industry, as well. I’ve grown my understanding and world view around the day to day of infosec. I try to add value to someone every single day. Those things keep me going and keep me engaged. They help minimize the burnout and maximize my patience with the often challenging task of being an infosec person and an entrepreneur. Sometimes, living to fight another day is all you can ask for, and some days it seems like you can’t wait to jump back into the fray. Such is the infosec (“cybersecurity”) life.

Advice for New Cybersecurity Practitioners:

If you’re new to cybersecurity or considering joining us, my advice to you is simple and a gut check. Be sure that you are ready for a career that requires life long learning and life long change. If you want to have a repeatable, 9-5 job that you can master and forget when you walk out the door, this probably isn’t for you. Attackers are amazingly dynamic, and thus, infosec must be just as dynamic as well. This isn’t an industry built for mastery – it’s an industry built for being a life long student. While that’s not always easy, it can be fun and rewarding. Got what it takes? I sure hope so – because we need help and we need it for today and the years to come…

MicroSolved vCISO for Credit Unions

I recently asked MicroSolved COO, Dave Rose, to share his thoughts with all of us about the vCISO program. He has been leading the effort this last year across several credit unions and regional banks around the US. I asked him for the 3 biggest benefits an organization can expect and here is what he said:

“MicroSolved has been providing vCISO services to Credit Unions for over 20 years. Whether you are a corporate or a natural person CU, hiring MSI for vCISO Services will allow you to:

  • Obtain CISO expertise without having to incur the expense of finding and hiring a CISO. This is an affordable solution that will help keep the risk budget under control.
  • MSI vCISO program comes with the benefit of a focus towards financial expertise and compliance. MSI has had extensive experience working with banks and credit unions on their risk programs, and have spent time educating regulators on risk events and controls.
  • MSI is in the business of mitigating risk. We live it everyday and our clients benefit from that experience. Our clients get to pick the risk work they want resolved and the issues they want remediated. 

You will be hard pressed to find a more efficient and cost effective way to address risk issues and move the regulatory needle. Don’t bear the burden of mitigating risk alone, let MSI be a partner to help you solve your risk needs!”

—Dave Rose

For more information, give us a call at 614-351-1237 or email us at info@microsolved.com.