Best Practices for Managing Browser Extensions in a Corporate Environment

 

In a world where efficiency is king, browser extensions have become the unsung heroes of productivity in corporate landscapes. These small software programs tailor browsing experiences to specific workflow needs, often becoming indispensable tools for employees. But this seemingly innocuous convenience can come with a hidden price: security.

In the delicate balance of utility and safety, IT departments are tasked with the crucial role of gatekeeping. They must rigorously vet and manage these extensions to avoid transforming productivity boosters into security liabilities. The challenge lies in crafting policies that protect without stifling innovation.

This article serves as a compass to navigate the complex terrain of browser extensions in a corporate environment. From understanding their significance to implementing stringent security protocols, identifying the risks of harmful add-ons, and ensuring continuous updates—every aspect converges on fortifying a company’s digital defenses while maintaining operational dexterity.

Why Browser Extensions are Important in a Corporate Environment

In today’s digital age, the importance of browser extensions in a corporate environment cannot be understated. With the increasing sophistication of cyber threats, organizations face various potential risks, including malware propagation, data leaks, and exploitation of security flaws. By managing browser extensions meticulously, enterprises can ensure that only trusted and vetted extensions are deployed within their networks, significantly reducing the hazard of security lapses.

Effective browser extension management tools are indispensable for enterprises aiming to govern the proliferation of these add-ons. Such tools grant the capability to restrict the distribution of non-compliant extensions and hinder the installation of those that may be outdated or malicious. Additionally, in bolstering the enterprise’s security posture, well-chosen and governed extensions can also play a pivotal role in augmenting productivity and improving workplace efficiency.

Indisputably, implementing a robust browser extension management strategy is a critical step towards safeguarding sensitive information, barricading unauthorized access attempts, and preserving a secure browsing experience for all users within the organizational framework.

Enhancing productivity and functionality

Browser extensions are not only pivotal for maintaining a strong security framework but are also instrumental in elevating productivity and functionality in the workplace. Take, for example, extensions like Gorgias that can significantly expedite the process of email communication. By facilitating the creation of templates and keyboard shortcuts for common responses, employees can drastically cut down on response times, thereby enhancing overall efficiency.

Moreover, the ability to customize keyboard shortcuts enables users to summon frequently employed phrases and templates at the press of a button, making repetitive tasks less time-consuming. Employing enterprise-grade browsers that offer enhanced control over unauthorized installs can further amplify security, consequently affording an environment where productivity tools are leveraged to their full potential without compromise.

To ensure the utmost safety and functionality, a thorough inspection of these extensions with specialized tools is essential. As such, only extensions that withstand rigorous safety checks become part of the workspace, cleanly integrating into the overall workflow without introducing security concerns.

Addressing specific business needs

Browser extension management transcends routine workflow optimization—it is a cornerstone for upholding stringent security and compliance standards within the enterprise. Leveraging a dedicated browser extension management tool is the linchpin in mitigating the risk presented by treacherous extensions that could threaten the organizational network’s integrity.

Products like Browser Security Plus empower IT administrators to orchestrate the dispersion of secure extensions while blocking those classified as malevolent. This ensures the network’s defenses remain impenetrable. Moreover, enterprise browsers, tailor-made for corporate demands, come with reinforced security features and sophisticated management abilities, thus, striking the perfect balance between functionality and security.

Centralized management of enterprise browsers via platforms such as Chrome Browser Cloud Management or Unified Endpoint Management systems allow IT teams to enforce security policies, gain visibility into security events, and robustly monitor browsing activities. This proactive stance on management ensures that the enterprise’s browsing ecosystem remains in lockstep with its larger security framework, all while adapting to the specific needs of the business.

Security Policies for Browser Extensions

In the contemporary digital workspace, enterprises need to be vigilant against security threats that continuously evolve in sophistication. One integral layer of defense comes from implementing rigorous security policies for browser extensions. These policies serve as a bulwark against malware, phishing attacks, and potential data loss, enabling an enterprise to maintain a secure browsing environment.

Security browser extensions proactively manage risks by offering a suite of features including content and URL filtering, secure browsing habits, and protection from inbound malicious threats. Furthermore, by enabling governance capabilities with varied policy settings, organizations can fine-tune control over the browsing experience, thereby tailoring security measures to the enterprise’s needs.

Having clear delineations of permissible actions, authentication requirements for particular operations, and rigorous control over sensitive data access are critical facets of enforcing these security policies. Such measures ultimately prevent unauthorized behavior, thus protecting the systems and data of an organization from the myriad of threats lurking within the digital realm.

Developing and enforcing strict security policies

The development and enforcement of stringent security policies revolve around detailed rule-making that governs browser extension use. By establishing policies, organizations can block access to certain websites, regulate the installation of plugins, and define user permissions. Such governance aligns security determinations with organizational requirements, paving the way to create a harmonized and secure browsing infrastructure.

These policies can be fine-grained to cater to an enterprise’s specific security and compliance mandates, ranging from mandatory extensions to those that are strictly forbidden. Executing these policies calls for a blend of restrictive measures, vigilant computer monitoring, real-time administrative controls, and robust agent-based web filters to enforce website blacklists and ensure compliance.

To bolster security efforts, these policies must be supplemented with malware and phishing protections, deploying AI for automatic threats detection. This technology provides real-time threat analysis and guides users away from potential risks, ensuring workplace browsing is a safe and regulated activity.

Defining acceptable and prohibited extensions

When it comes to regulating extensions, defining what is acceptable and what is not is paramount to maintaining security integrity. Acceptable extensions should align with business needs and pass through critical evaluation for safety before being sanctioned for use. Conversely, enterprises must be unwavering in prohibiting extensions that pose any risk of accessing and compromising sensitive corporate data.

Enforcing an effective extension policy requires not only blocking installations of unauthorized add-ons but also managing the permissions assigned to the extensions in use. By regulating these permissions, enterprises can control the level of access granted to devices, hence mitigating vulnerabilities.

Moreover, there must be strict controls to curb the proliferation of unnecessary administrative privileges. This minimizes the risk associated with compromised high-privilege accounts which could otherwise serve as gateways for security breaches.

Table 1: Extension Management Policy Guidelines

Policy Aspect

Description

Examples

Acceptable Extensions

Those vetted for aligning with business goals and safety.

Password Managers, VPNs, Productivity Tools

Prohibited Extensions

Those posing risks and unauthorized access to data.

Unvetted Social Media Plugins, Unknown Developer Tools

Permissions Management

Control over the extent of extension access to devices.

Limiting to Read/Write on specific sites or data

Admin Privilege Limitation

Prevention of excess high-privilege accounts.

Enforcing the principle of least privilege

Enforcing these policies with diligence ensures that enterprises can maintain a secure and productive browsing environment that contributes to their overall success.

Risks Posed by Malicious Extensions

In the digital workplace, the integration of browser and email plugins can streamline workflows and enhance efficiency. However, these tools also introduce significant security risks to the enterprise when malicious extensions enter the network. Malicious actors exploit browser extensions to carry out a range of harmful activities. They can automate clicking on pay-per-click ads for financial gains, collect sensitive user data without consent, and more alarmingly, intercept messages – including those from platforms like Gmail. There have been notable instances, such as a counterfeit ChatGPT extension, crafted to hijack Facebook accounts, showing how the semblance of legitimacy can mask a rogue extension’s true intent.

Owing to the insufficient screening of browser extension marketplaces, the gatekeeping of such plugins is often inadequate, leaving the door open for those with malicious intentions to enter. This laxity in oversight can lead to enterprise networks being hit with spam delivery, unauthorized saving of user inputs, and injection of harmful codes directly through the browser interface. These risks underscore the imperative need to exercise extreme caution and implement preemptive measures against the encroachment of hazardous browser plugins and extensions.

Not only can these extensions steal information like login credentials, but they can also harbor code-level vulnerabilities including bugs or outdated elements that can jeopardize the very integrity of the browsers and create security loopholes. In a preventative vein, enterprises can layer their security protocols with both technological and behavioral controls. This might involve barring employees from installing any extensions on business-operated devices and promoting the use of managed enterprise browsers to reduce exposure to such threats.

Understanding the potential security threats

Malicious browser extensions pose an array of potential risks that can compromise an organization’s security posture. Extensions that are poorly coded or have not been updated to patch known flaws become weak points through which attackers can launch their exploits. For instance, malicious entities can repurpose genuine extensions, creating counterfeit duplicates to deceive users. The repercussions of such deceptions range from the dissemination of spam to more dire consequences such as financial fraud.

With broad permissions in place, harmful extensions are well-placed to conduct undercover operations such as clicking on pay-per-click ads for profit, snooping on private user data, intercepting personal and professional communications, and carrying out account takeovers. These capabilities grant malicious extensions the potential to carry out espionage, fraud, and extortion.

Moreover, distinguishing safe from unsafe extensions is daunting due to the sheer number available. This challenge highlights the paramount importance of adopting a steadfast and proactive attitude toward cybersecurity. Organizations must not only rely on the utility and convenience that extensions provide but also remain acutely aware of the embedded risks they carry.

Identifying indicators of malicious extensions

To vigilantly combat the infiltration of malicious browser extensions, it is crucial to recognize their indicators. Such extensions often operate covertly, engaging in activities like secret clicks on monetized ads, wholesale collection of user data, access interception of private communications such as Gmail, and unauthorized control over social media accounts.

Cybercriminals exploit these tools to gain detailed insights into users’ browsing patterns, pilfer account credentials, and harvest Personally Identifiable Information (PII). Notorious examples of malware, such as Grandoreiro, Kimsuky, and Mispadu, have utilized malicious browser extensions to facilitate their data theft operations.

To deflect these security threats, enterprises must rigorously audit their systems to ensure all installed extensions are legitimate and do not harbor malicious intent. Instituting a browser extension whitelist, or more restrictively, a deny list, acts as a proactive execution prevention measure, effectively mitigating the risks associated with these potentially harmful plugins. A consistent review process and the ongoing education of employees about the dangers of unsanctioned extensions further fortify an organization’s defenses against these hidden dangers.

Table 2: Indicators of Malicious Extensions

Indicator

Description

Unusual Browser Behavior

Unexpected pop-ups or redirects to unknown sites

Unauthorized Ads Clicking

High ad activity without user interaction

Data Collection Anomalies

Spike in network traffic indicating data exfiltration

Account Irregularities

Unauthorized account access or messages sent

Extension Source Verification

Extensions not from verified developers or official stores

By maintaining persistent vigilance and implementing strict control measures, enterprises can safeguard their digital environments from the pernicious effects of malicious extensions, thereby preserving their operational integrity and their stakeholders’ trust.

Importance of Security Patches and Updates

In today’s fast-paced digital environment, the importance of security patches and updates cannot be overstated. With cyber threats constantly evolving, enterprises must remain vigilant by utilizing a comprehensive array of defensive measures. Web browsing proxies, content filtering, and email scanners are just some of the tools that can detect and thwart web threats before they ever reach user browsers. Browser security solutions serve as a crucial layer of defense, helping to close the gaps that malicious entities may exploit.

Notably, the implementation of automated patch management systems is central to maintaining the security perimeter. These systems ensure that browsers, operating systems, and all related software are up-to-date, minimizing the opportunities for cyber attackers to exploit known vulnerabilities. Regularly updating security patches and refining software versions add significant strength to the organization’s protection against the sophisticated and continuously evolving threats present in today’s browsing environment.

Furthermore, managing the array of extensions employees use is integral to maintaining a secure enterprise. Strict policies for managing these add-ons coupled with meticulous review processes can significantly enhance an organization’s security posture while also contributing to a more robust and streamlined user experience.

Table 1: Security Measures Enabled by Patches and Updates

Measure

Description

Web Threat Detection

Identifies potential threats through web browsing proxies and content filters.

Automated Patching

Streamlines the process of updating software to address security vulnerabilities.

Extension Management

Reviews and regulates browser and email plugins to prevent unauthorized activities.

Employee Training

Educates staff on threat recognition and avoidance techniques.

Continuous Monitoring

Ensures all systems and applications stay secure with the latest protective measures.

By following these practices, organizations can erect robust defenses against malicious activities, ensuring the continuity of their operations and the protection of sensitive data.

Staying up-to-date with the latest security patches

Amid an ever-changing cyber threat landscape, staying current with the latest security patches is a fundamental aspect of any robust cybersecurity strategy. Automated patching is indispensable as it guarantees that both browsers and operating systems operate on the latest and most secure versions available. An automated approach to patch management ensures continuous protection against vulnerabilities, making it a cornerstone of organizational security.

Security patches act as a critical defense mechanism to address exploitable flaws that could otherwise lead to data breaches or system intrusions. Consequently, a comprehensive patch management policy is vital for safeguarding networked hardware and software from these risks. Furthermore, the use of web browsing proxies and content filtering complements these efforts by proactively preventing threats from compromising user browsers.

Organizations must pair technical measures with human-centric strategies to fully fortify their security. This involves deploying regular training programs aimed at equipping employees with the skills to recognize and circumvent phishing attacks and other social engineering tactics. By merging these components, enterprises can create a multi-layered defensive infrastructure poised to counteract various cybersecurity challenges.

Implementing regular updates for enhanced security

Implementing regular updates is fundamental for maintaining an airtight security shield within an organization. Tools like Browser Security Plus monitor and promptly identify outdated plug-ins, which are common vectors for security breaches. In a corporate setting, where the stakes are invariably high, efficiently managing add-ons is a priority for upholding browser security.

Security solutions such as Symantec Endpoint Protection play a key role in equipping businesses with the capabilities to roll out fast and automatic updates. This agility is especially critical in the face of zero-day vulnerabilities, which require immediate attention to prevent exploitation. In the context of Chrome browser extensions, keeping them up-to-date is widely recognized as a best practice for enterprise security.

In managing browser extensions, enterprises can benefit from a range of strategies, such as the ability to block, enforce installation, or allow employee requests for extensions. These measures enhance overall browser security by giving organizations greater control over which extensions are permitted and ensuring that all permitted extensions are current and secure.

By embracing regular updates, businesses can significantly solidify their security stance. This proactivity not only mitigates risk but also instills confidence among stakeholders that their data and systems are well-protected against emerging threats.

Enhancing Security Posture with Proper Visibility

In an era where cybersecurity threats loom large, the importance of enhancing an organization’s security posture cannot be overstated. Proper visibility into user activities and system configurations is paramount to identifying threats and mitigating risks before they evolve into full-blown security incidents.

One of the first steps towards enhancing browser security is to track user activities including visited websites, downloaded files, and clicked links. This monitoring helps pinpoint potential threats and unusual behavior that may otherwise go unnoticed. Leveraging tools and services that provide real-time alerts and reports on these activities can significantly strengthen an enterprise’s defense mechanisms.

Gaining Insight into Security Events and Incidents

Visibility into security events and incidents is crucial for browser security management. By monitoring browser activities and configurations, IT administrators can gain valuable insights that inform the overall security strategy. It’s vital to track incidents such as password reuse, unsafe site visitations, and malware interactions. Identifying these events promptly allows for quick intervention and resolution, keeping the potential impact at a minimum.

Insights into security events can also stem from managing and tracking extension details and control movements. Approval workflows for browser extensions are essential in mitigating risks related to the permissions and capabilities granted to them. Additionally, comprehensive reporting of browser usage data—including browser versions, settings, and device information—plays a critical role in the analysis of security incidents.

Implementing Tools for Monitoring Extension Behavior

Tools like Browser Security Plus serve as an indispensable asset in monitoring the behavior of browser extensions. By distinguishing between signed and unsigned plugins, it offers a baseline assessment of the trustworthiness and safety of these components. Monitoring the permissions used by each extension sheds light on potential data security risks and helps enforce strict control over which functionalities are necessary and safe.

To effectively monitor extension behavior, IT administrators can employ tools that track not just website visits and file downloads but also detect modifications to browser settings. Watching for indicators of suspicious behavior, such as newly created files, unexpected network connections, processes, and registry key changes, is critical for holistic browser security. Before the enterprise-wide rollout, each browser extension or plugin must undergo a thorough inspection to certify its safety and reliability, thereby protecting the integrity of enterprise data and assets.

With these measures in place, organizations can significantly enhance their security posture by ensuring proper visibility and control over browser and email plugin activities within the enterprise.

Table 2: Tools and Strategies for Monitoring and Gaining Visibility

Tool/Strategy

Purpose

Benefit

Real-time User Activity Monitoring

Tracks websites visited, downloads, and link clicks

Identifies threats and unusual behavior

Extension Approval Workflows

Manages extension controls and permissions

Prevents potential vulnerabilities

Comprehensive Reporting

Gathers data on browser versions, settings, and device info

Assists in incident analysis and response

Signature Verification for Plugins

Differentiates between signed and unsigned plugins

Assesses plugin safety levels

Permission Usage Monitoring

Observes the permissions each extension utilizes

Identifies potential data security risks

Behavioral Analysis of Extensions

Detects file creation, network connections, and setting changes

Alerts to suspicious browser extension activity

Enterprises that integrate these monitoring tools and strategies into their security framework create a more transparent and secure online environment, shielding their infrastructure from the multitude of threats posed in the digital age.

Integrating with Active Directory for Seamless Management

When managing enterprise environments, the integration of browser and email plugin restrictions with Active Directory (AD) can provide a seamless and efficient centralized management experience. This integration is vital for ensuring that security policies are consistently applied across all users within the organization.

Leveraging Active Directory for centralized management

With Active Directory, configuring Group Policy Object (GPO) policies is crucial for the centralized management of browser extensions. In particular, when it comes to the installation of browser extensions, AD GPO policies take precedence, effectively becoming the highest priority and overriding any installation method—including SEP client registry values. This centralization means that IT administrators can ensure a consistent and controlled deployment, which is crucial for maintaining a secure and compliant enterprise network.

Active Directory’s Group Policy Object can also provide a streamlined approach for managing Chrome or Edge browser extensions. By utilizing the GPO, enterprises gain the ability to facilitate precise control over extension installation processes. This includes the power to prevent the installation of potentially unwanted or unauthorized extensions, which helps keep network traffic optimized by eliminating unnecessary downloads.

Active Directory Feature

Function

Impact on Management

GPO Policies

Centralized management of extensions

Overrules other installation methods

Installation Blocking

Prevention of extension installations with clients

Reduces unneeded network traffic

Add-on Management

Managing permissions and behaviors

Safeguards against vulnerabilities

Automating extension deployment and configuration

When it comes to the deployment and configuration of browser extensions, IT administrators can turn to automated solutions like Chrome Browser Cloud Management or Microsoft Group Policy Object (GPO). These platforms enable the remote installation of extensions on users’ browsers through policies such as the ‘Extension Install Forcelist’. Automating these processes not only saves time but also ensures that only authorized and necessary extensions are installed, adhering to the company’s security protocols.

To further tailor the user experience, enterprises often develop custom extensions that cater explicitly to their operational needs and then deploy these through specific policies. However, with the risk of malicious extensions that can compromise user data or inject harmful payloads, it’s recommended that enterprise environments restrict the installation of extensions on business-related devices. Security-first enterprise browsers can be configured to block unauthorized extension installs, mitigating potential security breaches before they happen.

In cases where organizations allow the installation of extensions, deploying tools to inspect and verify the security of these plugins becomes essential. These security checks help prevent any extensions with spammy behavior, suspicious permissions, or the potential to save user inputs from infiltrating the enterprise network.

By leveraging Active Directory for centralized extension management and automating the deployment of secure and custom extensions, enterprises can enhance their security posture while ensuring a robust and efficient operational environment.

Automation Tool

Purpose

Benefit

Extension Install Forcelist

Remote installation of extensions

Facilitates controlled, standardized deployment

Custom Extension Development

Craft extensions for specific needs

Meets precise enterprise requirements

Security Inspection Tools

Inspect and verify plugin safety

Prevents potential security threats

Utilizing these methodologies allows firms to maintain a strong security shield while providing users with the tools they need for productivity, without compromising on safety or control.

Efficient Management of Extension Permissions

With the ever-growing arsenal of browser extensions available, enterprises should meticulously manage the permissions such extensions are granted to ensure minimum privilege access. Permissions can act as a gateway for extensions to make changes on devices or manipulate web content under the guise of functionality. They are typically categorized into host permissions, which govern what web pages the extension can access or alter. A measured approach to assigning and overseeing these rights is germane to avert security risks akin to data theft or exploitation of browser vulnerabilities. By prudently defining and controlling the scope of access, organizations can foster an environment where security, compliance, and productivity coexist harmoniously.

A table illustrating effective permission management strategies:

Management Strategy

Objective

Benefit

Minimum Privilege

Grant only necessary permissions

Reduces risk of unauthorized data access

Host Permission Control

Define accessible web pages

Protects sensitive corporate content

Regular Audits

Review and adjust permissions

Ensures ongoing compliance and security

The efficacy of permission management lies in striking the perfect balance – allowing enough access for extensions to serve their purposed function without opening the floodgates to potential security breaches.

Controlling and Monitoring Extension Permissions

In the enterprise ecosystem, managing browser extensions by leveraging their permissions and limiting their access to only essential websites is a potent strategy for heightened security and more streamlined management. By utilizing tools and policies, such as the Runtime block hosts policy, organizations are equipped to dictate which websites extensions can interact with, thus securing critical sites from unauthorized script injections or data exfiltration attempts.

Organizations should deploy extension management tools that are pivotal in weaving a protective net capable of blocking malevolent extensions. Ensuring adherence to regulatory compliance and disseminating only vetted and safe extensions across the enterprise network also falls within the ambit of said tools. Key benefits to managing extension permissions proactively include time efficiency and a marked reduction in exposure to security vulnerabilities and potential data breaches, laying the groundwork for a fortified digital perimeter.

Monitoring Aspect

Action Item

Reasoning

Permission Requests

Assess and justify necessity

To avoid over-provisioning of access rights

Webpage Access

Limit to job-relevant domains

To minimize the risk of data compromise

Audit Trails

Maintain records of changes

For an accountability trail and easier review

Defining Role-Based Access to Minimize Risks

Role-based access control (RBAC) stands as a cornerstone in the enterprise defense strategy, concentrating on mitigating risks by aligning access permissions intricately with the specific roles and job functions within an organization. By enacting RBAC, enterprises can curtail the potential damage wielded by insider threats and curtail unauthorized glimpses into sensitive data and resources.

Effectively carving out roles and corresponding access levels enhances security measures by trimming down the attack surface. It also restricts the extent of potential security infringements. Adhering to the principle of least privilege, RBAC ensures individuals are endowed with just the right concoction of access privileges—nothing more, nothing less—vital for their responsibilities.

Here’s how role-based access control can be structured:

  1. Define roles: Identify and categorize job functions within the organization.
  2. Assign permissions: Grant access rights specifically suited to each role.
  3. Enforce restrictions: Implement technical blocks that enforce the assigned permission levels.
  4. Review regularly: Regularly reassess roles and permissions to keep up with changing job requirements and minimize stagnant access rights.

This methodical approach to defining role-based access is instrumental in buttressing the organization’s security posture, mitigating the likelihood of unauthorized activities, and therefore, diminishing the threat of data breaches in the digital enterprise landscape.

Summary

Implementing stringent browser and email plugin restrictions is essential in maintaining a secure enterprise environment. This ensures protection against the proliferation of malicious extensions that pose significant security risks. Utilizing tools such as Browser Security Plus can streamline this process by creating a secure repository of approved extensions, efficiently distributing them within the network while blocking harmful ones. Additionally, security browser extensions enhance an organization’s defenses against cyber threats, phishing, and malware through robust content filtering capabilities and policy management for safer browsing experiences.

Enterprises striving for a secure browsing infrastructure can benefit from the built-in security features and Chrome Browser Cloud Management, which emphasize Zero Trust principles and offer granular control and visibility over security events. Moreover, the Chrome Web Store’s review process for extensions adds a layer of security by requiring domain verification for installation, with options for private or unlisted deployment, manageable either manually or through policies like the Extension Install Forcelist. By enforcing active security policies, regular updates to security patches, and adhering to a strong security posture, enterprises can significantly mitigate risks and bolster their overall security infrastructure.

* AI tools were used as a research assistant for this content. MSI does not resell or endorse any products. All named products are examples only.

 

Segmenting Administrative Activities: 4 Options to Meet CIS Control 12.8

As organizations work to strengthen their cybersecurity posture, the CIS Critical Security Controls provide an excellent framework to build upon. In the latest Version 8 of the Controls, Control 12 focuses on establishing, implementing, and actively managing network devices to prevent attackers from exploiting vulnerable access points.

Within Control 12, Safeguard 12.8 specifically calls for enterprises to “segment administrative activities to dedicated machines, accounts, and networks.” This is critical for reducing the risk of credential compromise and lateral movement if an admin account is breached. But how exactly can organizations go about meeting this Control? Let’s look at four potential approaches.

 1. Dedicated Admin Workstations

One straightforward option is to provision separate physical workstations that are used exclusively for administrative tasks. These admin workstations should be hardened with strict security configurations and have limited network access. Ideally, they would have no direct internet connectivity and be logically separated from the primary corporate network.

Activities like managing network devices, administering user accounts, and accessing sensitive databases should only be performed from these dedicated and secured admin workstations. This greatly reduces the attack surface and opportunity for threats to compromise admin credentials.[1][2][3][8]

 2. Privileged Access Workstations (PAWs)

A similar but more formalized approach is to implement Privileged Access Workstations (PAWs). These are specially-configured systems that admins must log into to perform their privileged duties.

PAWs enforce strong authentication requirements, have limited internet access, and are tightly restricted in what applications and activities are allowed. They are typically used for the most sensitive admin functions like domain administration, server management, and access to confidential data. Microsoft provides extensive guidance on designing and deploying PAWs.[2][8]

 3. Jump Servers / Bastion Hosts

Another architectural option to segment administrative activities is to deploy hardened “jump servers” or “bastion hosts.” These are intermediary servers that admins must first connect to before accessing infrastructure systems and devices.

All administrative connections and activities are proxied through these closely monitored jump servers. Admins authenticate to the jump host first, then connect to target devices from there. This allows strict control and audit of administrative access without directly exposing infrastructure to potential threats.[3]

 4. Virtual Admin Environments

Virtualization and cloud technologies provide additional opportunities to segment admin activities. Organizations can provision logically isolated virtual networks, VPCs, virtual desktops, and other environments dedicated to administrative functions.

These virtual admin environments allow strict control over configurations, access, and permissions. They can be dynamically provisioned and decommissioned as needed. Admin activities like server management, network device configuration, and database administration can be performed within these controlled virtual environments, separated from general user access and systems.[8]

 Choosing the Right Approach

The optimal approach to meeting CIS Control 12.8 will depend on each organization’s unique network architecture, admin use cases, and risk considerations. Larger enterprises may utilize a combination of PAWs, jump servers, and virtual admin networks, while a smaller organization may find that a simple deployment of dedicated admin workstations meets their needs.

The key is to analyze administrative activities, determine appropriate segmentation, and enforce strict controls around privileged access. By doing so, organizations can significantly mitigate the risk and potential impact of compromised admin credentials.

Proper administrative segmentation is just one of many important security considerations covered in the CIS Critical Security Controls. But it’s an area where many organizations have room for improvement. Assessing current admin practices and determining how to further isolate and protect those privileged functions is well worth the effort to strengthen your overall security posture.

Citations:
[1] https://ppl-ai-file-upload.s3.amazonaws.com/web/direct-files/13705336/b11ecb11-ff34-4836-80b0-0b302497c10d/advice.pdf
[2] https://www.swarthmore.edu/writing/how-do-i-write-a-compelling-conclusion
[3] https://paper.bobylive.com/Security/CIS/CIS_Controls_v8_Guide.pdf
[4] https://www.masterclass.com/articles/how-to-write-a-conclusion
[5] https://www.cisecurity.org/controls/v8
[6] https://www.cisecurity.org/controls/cis-controls-navigator
[7] https://www.armis.com/blog/see-whats-new-in-cis-critical-security-control-12-version-8/
[8] https://www.youtube.com/watch?v=MaQTv8bItLk&t=78
[9] https://sprinto.com/blog/cis-controls/
[10] https://writingcenter.unc.edu/tips-and-tools/introductions/
[11] https://writingcenter.unc.edu/tips-and-tools/conclusions/
[12] https://www.mytutor.co.uk/blog/students/craft-excellent-conclusion/
[13] https://www.semrush.com/goodcontent/content-marketing-blog/how-to-write-an-introduction/
[14] https://blog.hubspot.com/marketing/write-stronger-introductions
[15] https://www.linkedin.com/advice/0/what-best-practices-writing-introduction-engages
[16] https://www.wordstream.com/blog/ws/2017/09/08/how-to-write-an-introduction
[17] https://www.reddit.com/r/writing/comments/1rjdyj/tips_on_writing_a_great_essay_conclusion/
[18] https://controls-assessment-specification.readthedocs.io/en/stable/control-12/index.html
[19] https://writingcenter.fas.harvard.edu/conclusions
[20] https://owl.purdue.edu/owl/general_writing/common_writing_assignments/argument_papers/conclusions.html

 

* AI tools were used as a research assistant for this content.

Maximize Your Cybersecurity: Discover How a Virtual CISO Can Transform Your Business Security Strategy

What is a vCISO?

A vCISO, virtual CISO, or virtual Chief Information Security Officer is a highly qualified cybersecurity expert who provides IT security and compliance services on a contractual basis. Unlike a full-time CISO, a vCISO works remotely and collaborates with an organization’s executive team to protect against security threats and ensure compliance with industry regulations.

As a cybersecurity expert, a vCISO brings years of experience and a wide range of skills. They deeply understand security practices, threat landscapes, and industry standards. With this knowledge, they can assess an organization’s security posture, identify potential gaps and risks, and develop a comprehensive cybersecurity strategy.

A vCISO’s role is to provide unbiased advice and guidance to the organization’s leadership team. They work closely with the executive team to align security objectives with business goals. VCISOs can help establish and implement security policies, compliance standards, and best practices by leveraging their technical expertise and industry knowledge.

By hiring a vCISO on a contractual basis, organizations gain access to a team of experts without the commitment of a full-time hire. This flexible and cost-effective approach allows businesses to benefit from the expertise of a seasoned professional while optimizing their security program. Ultimately, a vCISO helps organizations enhance their security posture and proactively mitigate cyber threats.

What does a virtual Chief Information Security Officer do?

A virtual Chief Information Security Officer (vCISO) plays a critical role in assisting organizations in developing and managing their information security program. One of the primary responsibilities of a vCISO is to create and implement a comprehensive security strategy for the organization. This includes identifying and prioritizing security threats, developing security policies and procedures, and establishing security controls to mitigate risks.

In addition to creating the security strategy, a vCISO coordinates and manages security audits conducted within the organization. They work closely with internal and external auditors to ensure the organization’s security practices and controls meet regulatory requirements and industry standards. This involves conducting risk assessments, reviewing security controls, and implementing necessary changes to enhance the organization’s security posture.

Furthermore, a vCISO evaluates third-party vendors and assesses their security capabilities. They ensure that third parties comply with the organization’s security requirements and implement necessary security measures to protect its data and systems from potential risks.

A crucial part of a vCISO’s role is presenting the organization’s security posture to stakeholders, such as the executive team and board members. They regularly update the organization’s security posture, including identified vulnerabilities or emerging threats. This helps stakeholders make informed decisions regarding the organization’s security investments and priorities.

A vCISO plays a vital role in helping organizations build a robust and effective information security program by fulfilling these responsibilities. They bring their expertise to develop a comprehensive security strategy, coordinate audits, evaluate third parties, and present the organization’s security posture to stakeholders.

Learning More

In conclusion, navigating the complex cybersecurity landscape can be daunting for any organization. However, partnering with a seasoned virtual Chief Information Security Officer (vCISO) can significantly enhance your security posture and ensure compliance with the latest industry standards. This is where MicroSolved comes into play. With our extensive experience and deep expertise in cybersecurity, we offer tailored vCISO services designed to meet your unique needs and challenges. Let us help you fortify your defenses, mitigate risks, and secure your digital assets effectively. Don’t wait for a security breach to realize the importance of expert guidance. Contact MicroSolved today and take a proactive step towards a more secure and resilient future.

 

* 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!

Brent’s Interview About His Most Recent Book

 

Introduction

In today’s digital age, the importance of cyber-security cannot be overstated. With threats evolving at an unprecedented rate, organizations need to be proactive in their approach to safeguarding their assets. “We Need To Talk: 52 Weeks To Better Cyber-Security” by L. Brent Huston offers a comprehensive guide to navigating the complex world of cyber-security. We sat down with the author to delve deeper into the inspiration, content, and significance of this book.

Interview

Q1: What inspired you to write “We Need To Talk: 52 Weeks To Better Cyber-Security”?

A1: As a virtual CISO and 30+ year security practitioner, I know how important it is to keep the security team engaged with one another, encourage open discussions, and do continual learning. I wrote the book to give security teams a good basis for these discussions every week for a year. Covering the basics and letting the team discuss sticking points and areas for improvement has led my clients to identify some interesting trends and rapidly mature their security programs. I think, literally, “We Need To Talk”. We need it as practitioners, individuals, teams, and organizations. This is a stressful, detail-oriented, rapid-change business, and talking helps nearly everyone involved.

Q2: Why did you feel it was essential to provide such a comprehensive view of cyber-security?

A2: So much of what we do is complex and touches multiple areas of our organization that we must bring the basics to each. I picked the topics for discussion in the book to address the high-level, technical, and procedural controls that almost every organization needs. I threw in some of the more tenacious topics I’ve encountered in my career and a few curve balls that have bitten us over the years. Information security and risk management are broad-spectrum careers, and we need a broad spectrum of topics to help security teams be successful.

Q3: Can you elaborate on how the structure of the book facilitates this year-long journey?

A3: This is a great question. The book idealizes a weekly security team meeting where the team discusses one of the topics and why it is relevant and then works through a series of questions to help them hone and refine their security program. The book includes a topic for each week, appropriate background information about that topic, and a set of questions for discussion by the team. As I piloted the book with my clients, it became clear that these were ultra-powerful discussions and led to some amazing insights. I knew then that I had to write and put the book out there to benefit security teams and practitioners.

Q4: How did leveraging AI tools shape the content and structure of the book?

A4: I used several AI tools to help generate the content of the book. It was written programmatically, in that I wrote some programming to leverage an AI backend to generate the questions and background information for each topic. I then adjusted the code and moderated the output until I got the book I wanted. It took a while, but it was fantastic when completed. I wanted to experiment with writing with AI tools, and since I knew the book I wanted to create had a specific format and content, it seemed like a good experiment. Ultimately, I learned much about working with AI and using Grammarly for editing and self-publishing. I have been absolutely thrilled with the response to the book and how the experiment turned out. In fact, it gave birth to another project that I am just beginning and will pave the way for some exciting new breakthroughs in how to work with AI tools in the coming years.

Q5: What is the one core message or lesson from your book that you’d like security teams to take away?

A5: The one takeaway I would have them consider is that discussion among the security team can really help a lot of the team members and the organization at large. We need to talk more about the work we do, both inside our teams and to the other teams we work with across the enterprise. The more we discuss, the more likely we can support each other and find the best solutions to our common problems and issues. Implementing the strategies, tactics, and insights we discover along the way might just be the change we need to make information security more effective, easier to manage, and even more fun!

Summary

L. Brent Huston’s “We Need To Talk: 52 Weeks To Better Cyber-Security” is more than just a book; it’s a roadmap for security teams to navigate the intricate maze of cyber-security. Through structured discussions, the book aims to foster collaboration, understanding, and growth among security professionals. With the unique blend of AI-generated content and Huston’s vast experience, this book promises to be an invaluable resource for those in the field.

 

* 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!

 

High-Level FAQ for Incident Response

  1. Q: What is an incident response process in information security?

A: The incident response process in information security is a systematic approach to identifying, containing, analyzing, and resolving security incidents that may compromise the confidentiality, integrity, or availability of an organization’s information systems and data. It involves a set of predefined policies, procedures, and tools designed to minimize the impact of security incidents and facilitate a swift recovery.

  1. Q: Why is the incident response process necessary?

A: The incident response process is crucial for organizations because it helps to minimize the damage caused by security incidents, protect sensitive data, maintain business continuity, and comply with regulatory requirements. A well-defined incident response process can also help organizations learn from security incidents and improve their overall security posture.

  1. Q: What are the critical phases of an incident response process?

A: The incident response process typically includes six key phases:

  • i. Preparation: Developing and maintaining an incident response plan, training staff, and setting up necessary tools and resources.
  • ii. Detection and Analysis: Identifying potential security incidents through monitoring, reporting, and analyzing security events.
  • iii. Containment: Limiting the spread and impact of an identified security incident by isolating affected systems or networks.
  • iv. Eradication: Removing the cause of the security incident, such as malware or unauthorized access, and restoring affected systems to a secure state.
  • v. Recovery: Restoring affected systems and networks to regular operation and verifying their security.
  • vi. Post-Incident Activity: Reviewing the incident response process, identifying lessons learned, and implementing improvements to prevent future incidents.
  1. Q: Who should be involved in the incident response process?

A: An effective incident response process involves a cross-functional team, typically called the Incident Response Team (IRT), which may include members from IT, information security, legal, human resources, public relations, and management. External stakeholders, such as law enforcement, third-party vendors, or cyber insurance providers, may also be involved, depending on the nature and severity of the incident.

  1. Q: How can organizations prepare for incident response?

A: Organizations can prepare for incident response by:

  • Developing a comprehensive incident response plan that outlines roles, responsibilities, and procedures for each process phase.
  • Regularly updating and testing the incident response plan to ensure its effectiveness and relevance.
  • Training employees on their roles and responsibilities during an incident, including reporting procedures and essential security awareness.
  • Establishing a well-equipped IRT with clear communication channels and access to necessary resources.
  • Implementing continuous monitoring and detection tools to identify potential security incidents early.
  1. Q: How can organizations improve their incident response process?

A: Organizations can improve their incident response process by:

  • Regularly reviewing and updating the incident response plan to reflect changes in the organization’s infrastructure, personnel, and threat landscape.
  • Conducting periodic tests and simulations, such as tabletop exercises or red team exercises, to evaluate the plan’s effectiveness and identify improvement areas.
  • Implement a continuous improvement cycle incorporating lessons learned from past incidents and industry best practices.
  • Investing in advanced detection and monitoring tools to enhance the organization’s ability to identify and respond to security incidents.
  • Providing ongoing training and support to the IRT and other stakeholders to ensure they remain up-to-date with the latest threats and best practices.

 

*This article was written with the help of AI tools and Grammarly.

SSL Certificate High-Level Best Practices

SSL certificates are an essential part of online security. They protect websites against hackers who try to steal information such as credit card numbers and passwords. In addition, they ensure that customers trust the site and its content.

Almost 50% of the top one million websites use HTTPS by default (they redirect inquiries of HTTP pages to URLs with HTTPS). (comodosslstore.com)As such, even pages that don’t deal with confidential data are being deployed using SSL. The underlying certificates to power the encryption are available from a variety of commercial providers, and even the pro-bono resource https://letsencrypt.org. No matter where you get your certificate from, here are a few resources for high-level best practices.

Trust Your Certificate Provider

Since certificates provide the basis for the cryptography for your site, their source is important. You can find a trustworthy list of providers for certificates here. https://www.techradar.com/news/best-ssl-certificate-provider. Beware of commercial providers not found on this list, as some of them may be sketchy at best, or dangerous at worst. Remember, the Let’s Encrypt project above is also highly trusted, even though they are not a commercial firm.

Manage Versions and Algorithms

Make sure you disable SSL and TLS 1.0 on the server. That version has known vulnerabilities. If possible, and there are no impacts on your users, consider removing 1.1 and 1.2 as well. 1.3 fixes a lot of the known issues with the protocol and supports only the known secure algorithms.

In cryptography, cipher suites play an important part in securing connections by enabling encryption at different levels. You shouldn’t be using an old version of a cryptographic protocol if there’s a newer one available; otherwise, you may put your site’s security at risk. Using secure cipher suites that support 128-bit (or more) encryption is crucial for securing sensitive client communications.

Diffie Hellman Key Exchange has been shown to be vulnerable when used for weaker keys; however, there is no known attack against stronger keys such as 2048-bits. Make sure you use the strongest settings possible for your server.

Manage and Maintain Certificate Expiration

As of Sept. 1, 2020, Apple’s Safari browser will no longer trust certificates with validity periods longer than 398 days, and other browsers are likely to follow suit. Reducing validity periods reduces the time period in which compromised or bogus certificates can be exploited. As such, any certificates using retired encryption algorithms or protocols will need to be replaced sooner. (searchsecurity.techtarget.com)

Maintain a spreadsheet or database of your certificate expiration dates for each relevant site. Make sure to check it frequently for expiring certificates to avoid user issues and browser error messages. Even better is to use an application or certificate management platform that alerts you in plenty of time to upcoming certificate expirations – thus, you can plan accordingly. Best of all, if possible, embrace tools and frameworks for automating certificate management and rotation – that makes sure that you are less likely to have expiration issues. Most popular web frameworks now have tools and plugins available to perform this for you.

Protect Your Certificates and Private Keys

Remember that your certificate is not only a basis for cryptography, but is also a source of identification and reputation. As such, you need to make sure that all certificates are stored properly, securely and in trusted locations. Make sure that web users can’t access the private certificate files, and that you have adequate back up and restore processes in place.

Make sure that you also protect the private keys used in certificate generation. Generate them offline, if possible, protect them with strong passwords and store them in a secure location. Generate a new private key for each certificate and each renewal cycle.

Revoke your certificate or keys as quickly as possible if you believe they have been compromised.

Following these best practices will go a long way to making your SSL certificate processes safer and more effective. Doing so protects your users, your reputation and your web sites. Make sure you check back with your certificate provider often, and follow any additional practices they suggest.

 

 

 

 

A vCISO Interview With Dave Rose

I had the pleasure to interview, Dave Rose, who does a lot of our virtual CISO engagements at MSI. I think you might enjoy some of his insights.

Q) In a few sentences, introduce yourself and describe your background that makes you a valuable virtual CISO. What are the keys to your success?

A) So my name is Dave Rose and I have been a CTO and in Technology for 25+ years. I started working daily with Risk as an Internal IT Auditor with the State of Ohio and expanded exponentially my knowledge and skills with JP Morgan Chase where I had day to day Risk responsibility for their Branch, ATM, Branch Innovation, Enterprise and Chase wealth Management applications. (548 to be exact!) What makes me a valuable CISO? In technology I have been audited by the best of them, SEC OCC,FINRA,Internal Audit, and been responsible for PCI and Basil compliance. I have had to review, implement and modify controls from NIST, ISO,SOX, GLBA, OWASP and CIS. In the financial industry I have worked with Agribusiness, Commercial Real Estate, Retail Banking, Investment Banking, Mutual Funds, Wealth Management, Credit Unions and 401K plans. As an IT/Operations manager/leader I have been responsible for Network Management, Finance, HR, Contract and Vendor Management, Help Desk, Development staff, Investment Operations, Sales, Cyber Engineers and Project Management, which I started my career performing. 

With the diversity that I listed above, there is a pretty good chance my past experience can help you to solve your current problems, now. A modicum of common sense, perseverance and a passion to do what right for the business while being responsible to the controls that make you successful has made me successful. 

Q) Speaking as a virtual CISO, what are some of the toughest challenges that your clients are facing this year?

A) I think that one of the biggest challenge that our clients are facing this year is Technology Deficit. I dont think this is anything new but with the deprecation of Win 7 and the threat of Ransomware, holding onto old technology with critical vulnerabilities is no longer an option. Whether is is hardware, software or code updates, companies cannot continue to mortgage technology debt to the future. Hate to be cliche but the time is now. 

Q) If you met with a board and they wanted to know what percentage of revenue they should be spending on information security, how would you answer that question?

A) I hate this question because it really does not have a good answer. A board asked me once “How much money would it cost me to get to a 3.5 on the NIST scale?” Money is only one facet of solving risk, there is culture, leadership, technology and business vision. Know and set the roadmap for all of those items for the next 5 years and your dollar investment will come naturally. So 6-7% (Rolls eyes)

Q) In terms of the NIST model, can you walk us through how you would prioritize the domains? If you came into a new organization, where would you start in the NIST model to bring the most value and what would the first 100 days look like?

A) There are two areas of the NIST model I would focus on, identify and protect. I would take a good hard look at access administration and all the components that make that up. Next I would look at log analysis and aggregation. I would spend the first hundred days doing a Risk Assessment of the entire environment but would also create a roadmap based on evaluation of current state for both Access Administration and Log Governance. Based on your results and determination of Risk and Reward (80/20 rule) map out the next 1-3 years. 

Q) If folks wanted to learn more about your insights or discuss having you work with them as a virtual CISO or security oversight manager, how can they reach you?

A) If you would like to talk further about these question, insights or would like to hear more about the MSI vCISO service, you can reach me at 614 372–6769, twitter @dmr0120 or e-mail at drose@microsolved.com!

Prepping for Incident Response

Prepping? Who wants to prep for incident response?

This particular bit of writing came from a question that I was asked during a speaking engagement recently – paraphrased a bit.

How can a client help the incident team when they’re investigating an incident, or even suspicious activity? 

So, I circulated this to the team, and we tossed around some ideas.

Continue reading

Ask The Experts: Why Do Security Testing of Internal Computer Networks?

Most organizations have realized the need to have vulnerability assessments of their internet-facing (external) computer networks performed periodically. Maybe they are alarmed by all the data compromises they hear about on the news or perhaps they are subject to regulatory guidance and are required to have vulnerability assessments done. But many organizations draw the line there and never have the security of their internal networks tested. This is a mistake! At least it’s a mistake if your goal is actually to protect your computer systems and the private information they store and process.

It is true that the most attacks against information systems come from external attackers, but that does not mean the internal threat is negligible. About one sixth of data compromises are due to employees and privileged insiders such as service providers and contractors. But there are many other reasons for testing the security of your internal networks besides the internal threat. For one thing, once cyber-criminals find a hole in your external defenses they are suddenly “insiders” too. And if your internal systems are not configured correctly, hardened and monitored, it becomes trivial for these attackers to own your systems and compromise all the private information you have.

The type of testing that gives you the most bang for the buck is internal vulnerability assessment. Doing this type of testing regularly has many benefits. One benefit that people usually don’t associate with internal vulnerability assessment is that it can be used to make maps and inventories of the network. These are essentials of information security. After all, if you don’t know what you have on your network and where it is, how can you protect it? Another benefit is that it allows you to view your internal network with perspective. In other words, it lets you see it the way an attacker would. It will reveal:

  • Access control issues such as default and blank passwords mistakenly left on the network during administration, open files shares or anonymous FTP sites that may contain private data or user accounts that are suspicious or inappropriate.
  • Systems that are missing security patches or that are running out of date software or operating systems that are no longer supported by the vendors.
  • Systems that have been misconfigured or that reveal too much information to unauthorized users.
  • Ports that are inappropriately left open or dangerous services such as Telnet or Terminal Services present on the network.
  • Poor network architecture that fails to properly segment and enclave information assets so that only those with a business need can access them.
  • How well third party systems present on your network are patched, updated and secured.

Also, from a business perspective, performing regular internal vulnerability assessments shows your customers that you are serious about information security; a factor that could influence them to choose your organization over others.

In addition to vulnerability testing, it is also more than just desirable to have penetration testing of the internal network performed occasionally. While vulnerability assessment shows you what flaws are available for attackers to exploit (the width of your security exposure), penetration testing shows you what attackers can actually do with those flaws to compromise your systems and data (the depth of your security exposure). Internal penetration testing can:

  • Reveal how attackers can exploit combinations of seemingly low risk vulnerabilities to compromise whole systems or networks (cascading failures).
  • Show you if the custom software applications you are using are safe from compromise.
  • Show you not only what is bad about your network security measures, but what is working well (this can really save you money and effort by helping you chose only the most effective security controls).

One other type of penetration testing that is well worth the time and expense is social engineering testing. As network perimeters become increasingly secure, social engineering techniques such as Phishing emails or bogus phone calls are being used more and more by attackers to gain a foothold on the internal network. We at MSI are very aware of just how often these techniques work. How well do you think your employees would resist such attacks?

Thanks to John Davis for this post.

Ask The Experts: Favorite HoneyPoint Component

This time around, we got a question from a client where HoneyPoint was being demoed for the experts.

Q: “What is your favorite component of HoneyPoint and why? How have you used it to catch the bad guys?”

Jim Klun started off with:

My favorite component is the simplest: HoneyPoint Agent. 

It’s ease of deployment and the simple fact that all alerts from an agent are of note – someone really did touch an internal service on a box where no such service legitimately exists – makes it attractive. 
No one will argue with you about meaning. 

I have recently seen it detect a new MSSQL worm (TCP 1433) within a large enterprise – information obtained from my own laptop. The Agent I had deployed on the laptop had a 1433 listener. It captured the payload from an attacking desktop box located in an office in another US state. 

The HoneyPoint Agent info was relayed to a corporate team that managed a global IPS. They confirmed the event and immediately updated their IPS that was – ideally – protecting several hundred thousand internal machines from attack. 

Honeypoint Agent: It’s simple, it works.

Adam Hostetler added his view:

I’m a simple, no frills guy, so I just like the regular old TCP listener component built into Agent. We have stood these up on many engagements and onsite visits and picked up unexpected traffic. Sometimes malware, sometimes a misconfiguration, or sometimes something innocuous (inventory management). I also find it useful for research by exposing it to the Internet.

John Davis closed with a different view:

My favorite HoneyPoint is Wasp. Watching how skilled attackers actually compromise whole networks by initially compromising one user machine gives me the shivers! Especially since most networks we see aren’t properly enclaved and monitored. If I were a CISO, knowing what is on my network at all times would be of primary importance; including what is going on on the client side! Wasp gets you that visibility and without all the traditional overhead and complexity of other end-point monitoring and white listing tools.

Have a question about HoneyPoint? Want to talk about your favorite component or use case scenario? Hit us on Twitter (@lbhuston or @microsolved). We can’t wait to hear from you. Feel free to send us your question for the experts. Readers whose questions we pick for the blog get a little surprise for their contribution. As always, thanks for reading and stay safe out there!