Third-Party Authentication Inventory Worksheet

Posted on May 31, 2024 by Brent Huston

We often get asked for worksheet questionnaires to help organizations inventory their third-party applications and the underlying authentication mechanisms.

As such, we have developed a template for our clients and others to use for this purpose.

You can easily distribute this worksheet to each part of the business or group, empowering them to complete it for each of their third-party applications.

Once they return the data, you can extract it into any aggregation tool or vendor monitoring system you use. If you don’t have those tools available, you can process and monitor them manually using this easy spreadsheet for each line of business.

You can get the template spreadsheet here.

As always, we hope these tools are helpful. Let us know if you have any questions or feedback.

FAQ on Software Inventory

Posted on June 16, 2023 by Brent Huston

1 What is software inventory?

Software inventory refers to keeping track of all software applications and operating systems installed on devices within a network.

2. Why is software inventory important for organizations?

Maintaining an accurate software inventory is essential for any organization. Without proper monitoring and control, unauthorized software and unmanaged devices can pose potential security risks for networks and sensitive data. Knowing which software applications and operating systems are being used can help organizations identify potential vulnerabilities and develop appropriate defense strategies.

3. How can organizations maintain an accurate software inventory?

Organizations can maintain an accurate software inventory by conducting a detailed inventory, implementing controls for unmanaged software, taking continuous inventory, establishing access controls, securing service accounts, maintaining audit logs, and conducting risk assessments.

4. What are the risks of not maintaining an accurate software inventory?

The risks of not maintaining an accurate software inventory include unauthorized software and potential security breaches, difficulty in incident response planning, and non-compliance with regulatory requirements.

5. What are the best practices for software inventory?

The best practices for software inventory include conducting a detailed inventory, implementing controls for unmanaged software, taking continuous inventory, establishing access controls, securing service accounts, maintaining audit logs, and conducting risk assessments.

6. How often should organizations conduct a software inventory?

Organizations should conduct a software inventory regularly (at least monthly) to ensure that all new software and changes to existing software are recorded and tracked.

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

Software Inventory

Posted on June 13, 2023 by Brent Huston

Background on Software Inventory and CIS CSC Version 8 Safeguards

Software inventory refers to keeping track of all software applications and operating systems installed on devices within a network. This process is crucial for ensuring all systems are updated and secure against potential security risks.

To help organizations maintain accurate inventories of software assets, the Center for Internet Security (CIS) has developed the Critical Security Controls (CSC) Version 8, which includes specific safeguards for software inventory.

These safeguards are designed to help organizations implement effective procedures for creating and maintaining an accurate inventory of all software assets. By following these best practices and safeguards, organizations can reduce their risk of security incidents and potential security breaches.

Why Software Inventory is Essential

A detailed inventory can also assist in incident response planning and audits. In the event of a security breach or threat, a comprehensive software inventory can provide a better understanding of the potential impact and how to mitigate it. Furthermore, audits require accurate documentation of assets, including software applications and versions, as this information is critical for compliance and risk management purposes. Overall, investing in a software inventory constitutes an essential aspect of cyber hygiene, serving as a foundational piece for defending against potential security threats.

In sum, maintaining an accurate inventory of software and hardware assets is critical for organizations. It can help reduce the risk of unauthorized software and potential security breaches, support incident response planning, and aid compliance and risk management efforts. By following industry-standard best practices, such as the CIS Critical Security Controls Version 8, organizations can ensure that software inventory procedures are implemented effectively and continuously monitored through ongoing assessment and continuous monitoring.

Best Practices for Software Inventory

Keeping an accurate and up-to-date software inventory is one of the most important steps to protect your organization from security breaches and cyber threats. The following are best practices for software inventory based on CIS CSC version 8 and industry-standard safeguards:

1. Conduct a detailed inventory: Identify all your software applications, versions, and supporting systems. This information should be organized in a way that is easy to access and understand and can be updated regularly.

2. Implement controls for unmanaged software: Unauthorized software poses a significant risk to your organization’s security. Ensure you have controls to prevent employees from installing unapproved software without your knowledge.

3. Take continuous inventory: Your software inventory should be ongoing. Regular checks ensure that all new software and changes to your existing software are recorded and tracked.

4. Establish access controls: Make sure that software applications are accessible only to individuals with a business need. This will help you minimize risks associated with uncontrolled access to software.

5. Secure service accounts: Service accounts have elevated privileges and access to your organization’s assets. Ensuring these accounts are managed and controlled to minimize potential risks is essential.

6. Maintain audit logs: Enable audit trails to track changes to your software inventory. Audit logs should be stored securely and only accessible to authorized personnel.

7. Conduct risk assessments: Regular risk assessments can help you identify vulnerabilities in your software inventory. This information can then be used to minimize risks and strengthen your security posture.

By following these best practices, you can ensure that you keep your software inventory up-to-date and secure. It is essential in preventing cyber threats and protecting your organization’s assets.

Software Inventory Sample Policy

Software inventory is a critical aspect of an organization’s security posture. It helps identify potential vulnerabilities and reduce an organization’s attack surface. This policy is designed to help organizations maintain an accurate software inventory and comply with the CIS Critical Security Controls.

1. Purpose

This policy aims to ensure that all software applications are identified, tracked, and continuously monitored to minimize the risk of unauthorized software and potential security incidents.

2. Scope

This policy applies to all software applications used within the organization and all individuals with access to these applications.

3. Policy

3.1 Software Inventory

An accurate inventory of all software applications and their versions must be maintained by the organization. This inventory must be updated regularly to reflect any changes to the software used by the organization.

3.2 Controls for Unmanaged Software

The installation of unapproved software on organization-owned devices is strictly prohibited. An approval process must be established to ensure that all software applications the organization uses are appropriately vetted, tested, and approved by authorized personnel.

3.3 Continuous Inventory

The software inventory must be continuously monitored to ensure new applications are promptly identified and logged. This process must include a review of access controls to minimize potential risks associated with unauthorized devices and software applications.

3.4 Access Controls

Access to software applications must be restricted to individuals who require the software to perform their job functions. Users must be adequately identified and authorized before granting access to any software application based on their job responsibilities.

3.5 Secure Service Accounts

Service accounts must be carefully monitored and controlled to minimize the risk of unauthorized access to organizational assets. Passwords for service accounts must be complex and changed regularly to maintain the account’s security.

3.6 Audit Logs

Audit logs must be implemented to track changes to the software inventory. These logs must be stored securely and accessible only to authorized personnel.

3.7 Risk Assessments

Regular risk assessments must be conducted to identify potential vulnerabilities in the software inventory. The results of these assessments must be used to develop appropriate controls to minimize risk.

4. Enforcement

Failure to comply with this policy could result in disciplinary action, including termination of employment.

5. Review

This policy will be reviewed and updated annually to ensure compliance with industry best practices and changing security requirements. Any changes to the policy must be approved by the organization’s security team.

Software Inventory Sample Procedures

Software Inventory Sample Procedures:

I. Identify and Classify Software:

a. Review organizational assets and identify software applications that are in use.

b. Classify software applications based on their level of security risk.

c. Assign each software application a unique identifier code.

II. Create a Software Inventory Database:

a. Develop a database to store the information gathered in step I.

b. The database must include the software application’s name, version, unique identifier code, and level of security risk.

c. Ensure access controls are in place for the database.

III. Create a Review Schedule:

a. Establish a schedule for continuously monitoring the software inventory.

b. Include a review of access controls during the review schedule.

IV. Perform Regular Audits:

a. Perform software inventory audits regularly.

b. Ensure unauthorized software is removed or approved according to the organization’s procedures.

V. Assess Risk:

a. Regularly assess risks associated with software in the inventory.

b. Identify potential vulnerabilities and determine appropriate controls.

VI. Implement Security Controls for Software:

a. Based on the risk assessment, implement security controls for the software in the inventory.

b. Monitor these controls regularly to ensure effectiveness.

VII. Document Changes and Updates:

a. Document all changes and updates to the software inventory database.

b. Assign a tracking number to the change or update.

c. Ensure that documentation is accessible only to authorized personnel.

VIII. Establish an Incident Response Plan:

a. Develop an incident response plan for potential security incidents.

b. Ensure the incident response plan includes software inventory control and management procedures.

IX. Conduct Regular Training:

a. Provide regular training to employees on the importance of software inventory management.

b. Ensure employees are aware of the organization’s policies and procedures related to software inventory control.

X. Continuously Monitor:

a. Continuously monitor the software inventory to ensure it is accurate and up-to-date.

b. Implement a system for reporting and tracking anomalies or changes found during monitoring.

By following these procedures, your organization will be able to comply with the CIS Critical Security Controls and industry-standard best practices for software inventory management. Regular review and monitoring of the inventory will reduce the risk of unauthorized software installations and potential security incidents.

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

FAQ on Hardware Inventory

Posted on May 22, 2023 by Brent Huston

1. What is hardware inventory?

Hardware inventory is the comprehensive tracking and management of all hardware assets owned by an organization, including desktops, laptops, servers, and network devices. It is a required baseline control in CIS CSC Version 8 and most other best practices and regulatory guidance.

2. Why is hardware inventory important?

Hardware inventory is important because it allows organizations to better understand their attack surface and potential vulnerabilities by maintaining a detailed inventory. This data can be used to optimize hardware purchases over time, especially when performance data is also tracked.

3. How often should a hardware inventory be conducted?

It is recommended that a physical inventory of hardware assets be conducted at least once a year or when significant changes occur in the organization.

4. What information should be documented for each hardware asset?

All relevant information for each asset should be recorded, including make, model, serial number, location, owner, and software installed. Performance data is also a plus.

5. Where can I get sample policies and procedures?

You can find some sample policies and procedures here: https://stateofsecurity.com/hardware-inventory/

Hardware Inventory

Posted on May 15, 2023 by Brent Huston

Background on Hardware Inventory and CIS CSC Version 8 Safeguards

As technology advances, so do the security risks that come with it. To mitigate cybersecurity threats, organizations need to implement strict security measures. One such measure is the implementation of hardware inventory procedures that align with CIS CSC Version 8 safeguards and industry-standard best practices.

Hardware inventory procedures involve the comprehensive tracking and management of all hardware assets owned by an organization. This includes everything from desktops and laptops to servers and network devices. Organizations can better understand their attack surface and potential vulnerabilities by maintaining a detailed inventory.

CIS CSC Version 8 safeguards outline a set of 18 critical security controls that are considered best practices for securing an organization’s network and data. These controls cover various security requirements, including access control, incident response planning, and audit log management.

When it comes to hardware inventory specifically, the following CIS CSC Version 8 safeguards are crucial:

– Inventory of Authorized and Unauthorized Devices: This safeguard involves creating and maintaining a detailed inventory of all authorized and unauthorized devices. By doing so, organizations can more easily detect and remove any unauthorized devices that could potentially pose a security risk.

– Inventory of Authorized and Unauthorized Software: Similar to the above safeguard, this control involves maintaining a detailed inventory of all authorized and unauthorized software. This way, organizations can ensure that only authorized software is used on their hardware, which helps maintain a security posture.

– Secure Configurations for Hardware and Software on Mobile Devices, Laptops, Workstations, and Servers: By implementing secure configurations for hardware and software, organizations can minimize any vulnerabilities.

Implementing these CIS CSC Version 8 safeguards, in addition to industry-standard best practices, can help organizations to create a strong security posture and protect against security breaches and other potential impacts.

Why Hardware Inventory is Essential

Hardware inventory may seem tedious and time-consuming, but it is essential for any organization that wants to maintain a solid cybersecurity posture. Keeping track of every piece of hardware owned by the organization not only helps to prevent unauthorized access but also enables you to identify potential security risks and vulnerabilities in your network. It’s essential to know what hardware you have, where it’s located, and what software is installed on it, especially when dealing with many devices.

Failure to maintain a detailed hardware inventory could result in security breaches, where malicious actors gain access to your network and sensitive information. An organized and up-to-date inventory helps to streamline audits, improve compliance, and quickly identify any changes to the hardware or software environment. By knowing what you have and what you need, organizations can implement appropriate controls to protect their assets from cybersecurity risks more effectively. Furthermore, the inventory could also help identify under-utilized or over-utilized equipment, providing insights for better, data-driven decisions in managing assets.

In conclusion, hardware inventory is critical in securing an organization’s infrastructure and safeguarding sensitive information. It enables organizations to identify assets, keep track of changes, and detect any vulnerabilities that could pose a threat. A detailed inventory helps implement appropriate controls to mitigate risks, improving an organization’s overall cybersecurity posture. Therefore, every organization should take the time to maintain an up-to-date list of their hardware assets to ensure they remain protected against cyber threats.

Best Practices for Hardware Inventory

Having a detailed and up-to-date inventory of your hardware is essential in maintaining your organization’s security. Here are some best practices based on CIS CSC version 8 to help you maintain a secure hardware inventory:

1. Conduct a regular inventory: It is recommended that you conduct a physical inventory of your hardware at least once a year or when significant changes occur in your organization.

2. Identify assets: You should identify all the hardware assets that require inventory, including servers, desktops, laptops, tablets, and smartphones.

3. Document all information: Record all the relevant information for each asset, including make, model, serial number, location, owner, and software installed.

4. Asset management: Use a centralized asset management system to maintain an accurate inventory and track changes or updates.

5. Establish access controls: Ensure only authorized personnel have access to the hardware inventory and limit their access to only the required information.

6. Conduct regular audits: Regular audits ensure your inventory is accurate and up-to-date. Make sure that all changes are documented for future reference.

7. Implement Threat Prevention: Establish threat prevention measures for hardware, such as installing security software, monitoring for unauthorized changes, and training employees to recognize and report potential security threats.

8. Develop an incident response plan: Develop an incident response plan that outlines how to respond to any security incidents related to your hardware inventory.

By following these best practices, you can maintain a secure and efficient hardware inventory and protect your organization from potential security risks.

Hardware Inventory Sample Policy

Our organization takes cybersecurity seriously and strives to maintain a robust security posture that protects our assets and our customers’ data. As part of our efforts to mitigate potential security risks, we have established a strict policy for hardware inventory that complies with the CIS CSC Version 8 Safeguards and Industry Standard Best Practices.

1. Regular Inventory: We will conduct a physical inventory of all our hardware assets at least once a year or whenever significant changes occur in our organization. This will ensure that we have an accurate and up-to-date inventory of all our hardware assets.

2. Identify Assets: We will identify all the hardware assets that require inventory, including servers, desktops, laptops, tablets, and smartphones. This will help us keep track of all our hardware assets and prevent security breaches.

3. Document Information: We will carefully document all relevant information for each asset, including make, model, serial number, location, owner, and software installed. This will help us maintain an accurate inventory of our hardware assets and facilitate quick identification in case of any security incidents.

4. Asset Management: We will use a centralized asset management system to maintain an accurate inventory and track changes or updates. This will help us keep track of all our hardware assets and ensure our inventory is always current.

5. Access Control: Access controls will be established to ensure only authorized personnel can access the hardware inventory and limit their access to only the required information. This will help us prevent unauthorized access to our hardware inventory and mitigate potential security risks.

6. Regular Audits: We will conduct regular audits to ensure our inventory is accurate and up-to-date. Any changes to our inventory will be documented for future reference. This will help us identify any discrepancies and correct them quickly.

7. Threat Prevention Measures: We will establish threat prevention measures for hardware, such as installing security software, monitoring unauthorized changes, and training employees to recognize and report any potential security threats. This will help us prevent any security breaches and mitigate potential security risks.

8. Incident Response Plan: We will develop an incident response plan that outlines how to respond to any security incidents related to our hardware inventory. This will help us respond quickly and efficiently to security incidents and prevent data breaches.

By following this policy, we can ensure the security and integrity of our hardware inventory, mitigate potential security risks, and protect our organization’s assets and our customers’ data.

Hardware Inventory Sample Procedures

Hardware Inventory Sample Procedures:

1. Regular Physical Inventory Check-ups: Perform a physical inventory of all hardware assets at least once a year or whenever major organizational changes occur. This ensures an accurate and up-to-date inventory of all hardware assets is maintained.

2. Identify Hardware Assets: Identify all hardware assets that require inventory, including servers, desktops, laptops, tablets, and smartphones. Accurately identifying these assets helps track them and prevents any security breaches.

3. Document Information: Document all relevant information about each hardware asset, including make, model, serial number, location, owner, and software installed, to maintain an accurate inventory of assets. The documentation helps quickly identify all hardware assets in case of any security incidents.

4. Use a Centralized Asset Management System: Establish a centralized asset management system to maintain an accurate inventory and track any changes or updates to the hardware asset details. This helps keep track of all hardware assets and ensures the inventory is always current.

5. Control Access: Establish access controls to ensure only authorized personnel have access to the hardware inventory and only to the information they require. This helps prevent unauthorized access to the hardware inventory, mitigating potential security risks.

6. Conduct Regular Audits: Regularly audit the hardware inventory to ensure accuracy and that it is up to date. Any changes to the inventory should be documented for future reference. This helps identify any discrepancies and correct them quickly.

7. Install Threat Prevention Measures: Establish threat prevention measures, such as installing security software, monitoring for unauthorized changes, and training employees to recognize and report potential security threats. This helps prevent security breaches and mitigate potential security risks.

8. Create an Incident Response Plan: Develop an incident response plan that outlines how to respond to any security incidents related to hardware inventory. This helps respond quickly and efficiently to any security incidents and prevent potential data breaches.

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

3 Tips for Locating and Identifying IoT Devices On Your Enterprise Networks

Posted on March 8, 2023 by Brent Huston

Are you confident that your enterprise networks are secure? If so, can you be certain all approved IoT devices are accounted for and properly configured? It’s essential to identify every device connected to your network if only to ensure that it is not a malicious actor.

But identifying unauthorized network intruders is not the only reason for carefully inspecting your enterprise networks.

In this article, I’ll provide 3 tips for locating and identifying any Internet of Things (IoT) Devices on your enterprise networks. These tips will help you reduce vulnerability across your entire organization and ensure maximum data security.

Scan The Network

One of the best ways to locate and identify IoT devices on your enterprise networks is to scan the network for any active connections. This can be done using various tools such as nmap or a vulnerability scanning product. By scanning the network, you can see which devices are connecting to your network and get some idea of what they might be. Some tools, including nmap can guess the type of device it might be based on stack fingerprinting or services identified.

Scan For BlueTooth Devices

Many IoT devices use Bluetooth to connect to other devices or interact with users, and scanning for such devices can help you locate them. You can use a tool such as BLE Scanner to detect any active Bluetooth devices connected to your network. This will help you identify unapproved or unauthorized Bluetooth-enabled IoT devices on your networks.

Inventory MAC Addresses And ARP Data

Every IoT device connected to your network has a unique MAC address. By keeping an inventory of all the active MAC addresses, you can quickly identify any new or unauthorized devices connecting to your networks. Additionally, you should monitor ARP data for changes or anomalies. Detecting any suspicious activity could indicate that a malicious actor or unexpected device is attempting to connect to your network.

To look up the MAC address and identify the vendor of an IoT device, you can search using the MAC address on websites such as macvendors.com, which will show you who manufactured the device. Some network security and monitoring systems may also provide a way to look up MAC addresses, allowing you to identify any unauthorized devices on your enterprise networks quickly.

In conclusion, ensuring that all IoT devices connected to your enterprise networks are identified and adequately configured is essential. To do this, you should scan the network for active connections, scan for Bluetooth devices, and inventory MAC addresses and ARP data.

FAQ for Enterprise Authentication Inventory

Posted on February 10, 2023 by Brent Huston

Q: What is authentication inventory?

A: Authentication inventory is the process of identifying and documenting all of the systems and applications that require remote access within an organization, as well as the types of authentication used for each system and any additional security measures or policies related to remote access.

Q: Why is authentication inventory important?

A: Authentication inventory is important because it helps organizations protect themselves from credential stuffing and phishing attacks. By having a complete and accurate inventory of all points of authentication, organizations can ensure that the right security protocols are in place and that any suspicious activity related to authentication can be quickly identified and addressed.

Q: What steps should I take to properly inventory and secure my authentication points?

A: To properly inventory and secure your authentication points, you should: 1) Identify the different types of authentication used by the organization for remote access; 2) List all of the systems and applications that require remote access; 3) Document the type of authentication used for each system/application and any additional security measures or policies related to remote access; 4) Check with user groups to ensure that they use secure authentication methods and follow security policies when accessing systems/applications remotely; 5) Monitor access logs for signs of unauthorized access attempts or suspicious activity related to remote access authentication; 6) Regularly review and update existing remote access authentication processes as necessary to ensure accurate data.

Inventorying Organization Authentication Points

Posted on January 2, 2023 by Brent Huston

Are you looking for threat-proactive ways to secure your enterprise? One of the best ways to do this is by inventorying all of the points of authentication within your organization. In this blog post, we’ll discuss the steps you need to take to properly inventory and secure your Internet-facing authentication points. While you should have a complete and accurate inventory of these exposures, starting the process with a focus on critical systems is a common approach.

Inventory Process

1. Identify the different types of authentication used by the organization for remote access (e.g. passwords, two-factor authentication). If possible, use vendor data to include cloud-based critical services as well.

2. List all of the systems and applications that require remote access within the organization. External vulnerability scanning data and Shodan are both useful sources for this information.

3. For each system/application, document the type of authentication used and any additional security measures or policies related to remote access (e.g., password complexity requirements). Vendor management risk data can be useful here, if available.

4. Check with user groups to ensure that they use secure authentication methods and follow security policies when accessing systems/applications remotely.

5. Monitor access logs for signs of unauthorized access attempts or suspicious activity related to remote access authentication.

6. Regularly review and update existing remote access authentication processes as necessary to ensure the continued security of organizational resources over the Internet.

Why This Is Important – Credential Stuffing & Phishing

Inventorying all of the points of authentication within an enterprise is essential as protection against credential stuffing and phishing attacks. Credential stuffing is a type of attack where malicious actors use stolen credentials to gain access to different accounts, while phishing attacks are attempts to acquire confidential information through deceptive emails or websites. In both cases, it is important that organizations have proper authentication measures in place to prevent unauthorized access. Inventorying all of the points of authentication within an organization can ensure that the right security protocols are in place and that any suspicious activity related to authentication can be quickly identified and addressed.

In addition, having a detailed inventory of all points of authentication can help organizations identify any weak spots in their security measures. This allows them to take steps to strengthen those areas and further protect themselves from potential credential stuffing or phishing attacks. By regularly reviewing and updating their authentication processes, organizations can ensure that their resources remain secure and protected from any malicious actors.

Lastly, ensure that you feed this inventory and the knowledge gained into your enterprise risk assessment processes, incident response team, and other security control inventories. Make a note of any security gaps identified during the inventory process and ensure complete coverage of the logs and other intrusion detection systems at each potential point of authentication. By following these steps, you can ensure that your enterprise remains secure and protected from any potential threats associated with credential stuffing and credential theft associated with common phishing attacks.

Introducing AirWasp from MSI!

Posted on November 15, 2016 by Brent Huston

NewImage

For over a decade, HoneyPoint has been proving that passive detection works like a charm. Our users have successfully identified millions of scans, probes and malware infections by simply putting “fake stuff” in their networks, industrial control environments and other strategic locations.

Attackers have taken the bait too; giving HoneyPoint users rapid detection of malicious activity AND the threat intelligence they need to shut down the attacker and isolate them from other network assets.

HoneyPoint users have been asking us about manageable ways to detect and monitor for new WiFi networks and we’ve come up with a solution. They wanted something distributed and effective, yet easy to use and affordable. They wanted a tool that would follow the same high signal, low noise detection approach that they brag about from their HoneyPoint deployments. That’s exactly what AirWasp does.

We created AirWasp to answer these WiFi detection needs. AirWasp scans for and profiles WiFi access points from affordable deck-of-cards-sized appliances. It alerts on any detected access points through the same HoneyPoint Console in use today, minimizing new cost and management overhead. It also includes traditional HoneyPoints on the same hardware to help secure the wired network too!

Plus, our self-tuning white list approach means you are only alerted once a new access point is detected – virtually eliminating the noise of ongoing monitoring.

Just drop the appliance into your network and forget about it. It’ll be silent, passive and vigilant until the day comes when it has something urgent for you to act upon. No noise, just detection when you need it most.

Use Cases:

Monitor multiple remote sites and even employee home networks for new Wifi access points, especially those configured to trick users
Inventory site WiFi footprints from a central location by rotating the appliance between sites periodically
Detect scans, probes and worms targeting your systems using our acclaimed HoneyPoint detection and black hole techniques
Eliminate monitoring hassles with our integration capabilities to open tickets, send data to the SIEM, disable switch ports or blacklist hosts using your existing enterprise products and workflows

More Information

To learn how to bring the power and flexibility of HoneyPoint and AirWasp to your network, simply contact us via email (info@microsolved.com) or phone (614) 351-1237.

We can’t wait to help you protect your network, data and users!