Skip to content

Regulations & Standards
- HIPAA
- ISO/IEC 27001
- NERC CIP
- PCI DSS
- Browse all
Frameworks
Services
Resources
- Latest News
- Blog
- Reports
- Data Sheets
- White Papers
About
FAQ

Menu

Regulations & Standards
- HIPAA
- ISO/IEC 27001
- NERC CIP
- PCI DSS
- Browse all
Frameworks
Services
Resources
- Latest News
- Blog
- Reports
- Data Sheets
- White Papers
About
FAQ

About
FAQ
Log in / Joins us

About
FAQ
Log in / Joins us

Regulations & Standards
- HIPAA1. What is HIPAA? The Health Insurance Portability and Accountability Act of 1996 (HIPAA) is a federal legislation that set forth national standards to safeguard sensitive patient health information from unauthorized disclosure without the patient’s knowledge or consent. The HIPAA regulation consists of four rules: 1. Privacy Rule The Privacy Rule is designed to guarantee that entities handling health information implement appropriate measures to safeguard the information from unauthorized access or disclosure.Empower individuals with the knowledge and control over how their health information is utilized. Adherence to the Privacy Rule assures individuals seeking healthcare that an organization is dedicated to preserving the confidentiality and security of their information. Even if individuals are not interacting directly with an organization, they can trust the HIPAA framework to maintain the privacy of their data across all involved parties. 2. Security Rule The Security Rule is focused on protecting a specific subset of information encompassed by the Privacy Rule by establishing standards for the protection of electronically stored and transmitted PHI (ePHI). This is achieved by mandating the implementation of administrative, technical, and physical safeguards. Compliance with the Security Rule signifies an organization’s dedication to safeguarding the confidentiality, integrity, and security of ePHI, and…
  - Find the right software for your HIPAA compliance needs by comparing software capabilities, covered requirements, compliance impact, and the level of evidence the software supports. The HIPAA (Health Insurance Portability and Accountability Act of 1996) is a U.S. law that mandates national standards for protecting sensitive patient health information, known as protected health information (PHI).
- ISO/IEC 270011. What is ISO/IEC 27001? ISO/IEC 27001 is an internationally acknowledged standard, belonging to the ISO/IEC 27000 series, that outlines the requirements for managing an organization’s information security program through a well-defined ISMS. 2. What is an ISMS (Information Security Management System)? An Information Security Management System (ISMS) is a comprehensive set of documents, which includes policies, processes, procedures, and controls, designed to facilitate effective risk management. When developing your ISMS, it is crucial to ensure that the controls, policies, and procedures you implement address the following key information security objectives: Confidentiality: Guaranteeing that data is accessible only to authorized individuals. Integrity: Ensuring that data remains complete and accurate at all times. Availability: Ensuring that data is readily accessible to authorized individuals when needed. ISO/IEC 27001 is structured into 10 sections (referred to as “clauses” in ISO/IEC 27001 terminology) and one annex. The first three clauses provide an introductory overview of the process, while clauses 4 to 10 offer more strategic guidance for securing the business as a whole. Each clause provides a set of guidelines designed to enhance your organization’s security posture. Besides these clauses, ISO/IEC 27001 also includes a single annex, known as Annex A. This annex consists…
  - Identify the appropriate software solution for your ISO/IEC 27001 compliance needs. Evaluate software capabilities, covered requirements, compliance impact, and determine the level of evidence the software provides. ISO/IEC 27001 is an internationally acknowledged standard, belonging to the ISO/IEC 27000 series, that outlines the requirements for managing an organization’s information security program through a well-defined ISMS.
- NERC CIP1. What is NERC CIP? NERC CIP, which stands for North American Electric Reliability Corporation Critical Infrastructure Protection, is a collection of cybersecurity standards devised to safeguard the vital infrastructure of the North American electric grid. The objective of NERC CIP standards is to guarantee the reliability, security, and resilience of the electric power system by setting requirements for the identification and protection of critical assets and confidential information. Below is a summary of the NERC CIP framework: CIP-002: Critical Cyber Assets Identification: This requirement is centered on the identification and categorization of critical cyber assets within an organization’s control systems that are essential for the reliable operation of large-scale energy systems. CIP-003: Security Management Controls: This requirement is centered on the implementation of security management controls to establish and maintain an effective cybersecurity program. This encompasses the development of policies, conducting risk assessments, and implementing security controls. CIP-004: Personnel and Training: This requirement underscores the significance of qualified personnel and appropriate training to support an organization’s cybersecurity initiatives. CIP-005: Electronic Security Perimeter: This requirement is centered on establishing secure electronic access points or security perimeters to shield critical cyber assets from unauthorized access and cyber threats. CIP-006: Physical Security…
  - Select the best software solution for your NERC CIP compliance. Compare software capabilities, covered requirements, compliance impact, and evaluate the effectiveness of the evidence provided by the software. NERC CIP (North American Electric Reliability Corporation Critical Infrastructure Protection) is a set of cybersecurity standards designed to protect the critical infrastructure of the North American electric grid.
- PCI DSS1. What is PCI DSS? Companies that store, process or transmit cardholder data are required to comply with the Payment Card Industry Data Security Standard (PCI DSS). This standard defined by the Payment Card Industry Security Standards Council (PCI SSC) specifies technical and operational requirements established to protect cardholder data, in-scope data includes the sensitive authentication data (stored on magnetic stripe data or equivalent on a chip, CVC2, CVV2, CID, PINs, PIN blocks) and the primary account number (PAN). The PCI SSC is responsible for managing the security standards, while compliance with the PCI set of standards is enforced by the founding members of the Council, American Express, Discover Financial Services, JCB International, MasterCard Worldwide and Visa Inc. Companies must undergo an annual security audit and quarterly network scan by PCI SSC approved providers. Not complying with the PCI DSS standard could lead to fines of non-compliance up to $500,000, expensive litigation costs, and being barred from cardholder data processing from card schemes. Furthermore, non-compliance has a direct impact on brand reputation and exposes companies to negative publicity that damages consumer confidence. The PCI DSS is composed of 12 requirements, organized into six control objectives: Build and Maintain a Secure…
  - Choose the appropriate software solution for your PCI DSS compliance. Evaluate software capabilities, covered requirements, compliance impact, and evaluate the effectiveness of the evidence provided by the software. PCI DSS (Payment Card Industry Data Security Standard) specifies technical and operational requirements established to protect cardholder data, in-scope data includes the sensitive authentication data and the primary account number (PAN).
- Browse all
Frameworks
- MITRE ATT&CK®1. What is MITRE ATT&CK? The MITRE ATT&CK is a comprehensive cybersecurity knowledge base of adversary tactics and techniques, grounded in actual real-world observations. This knowledge base provides a standardized approach to understanding, categorizing, and analyzing cyber threats and attack techniques. The MITRE ATT&CK was developed by MITRE, a nonprofit entity, established to offer engineering and technical advice to the federal government. The MITRE ATT&CK focuses on adversary behavior and provides insights into how cyber threats operate, their tactics, techniques, and procedures (TTPs), and the different stages of a cyber-attack. It is widely used in the cybersecurity industry and is valuable for organizations seeking to enhance their threat detection, incident response, and overall cybersecurity defenses. MITRE ATT&CK consists of a matrix that categorizes cyber threats based on the different stages of an attack, known as the “ATT&CK Matrix.” It includes the following components: Tactics: The high-level objectives that adversaries aim to achieve during a cyber-attack. These tactics include initial access, execution, persistence, privilege escalation, defense evasion, credential access, discovery, lateral movement, collection, exfiltration, and impact. Techniques: The specific methods and techniques used by adversaries to accomplish their objectives within each tactic. These techniques describe the step-by-step actions and procedures employed…
  - Select the appropriate software solution for MITRE ATT&CK mitigations by comparing software capabilities and covered mitigations supported by the software. MITRE ATT&CK is a comprehensive cybersecurity knowledge base of adversary tactics and techniques, based on real-world observations.
- NIST CSF1. What is NIST CSF? The National Institute of Standards and Technology (NIST) Cybersecurity Framework (CSF) is a widely recognized and widely adopted framework that provides a set of guidelines, best practices, and standards for improving cybersecurity risk management. The framework is specifically designed to help organizations, including critical infrastructure sectors, identify, protect, detect, respond to, and recover from cyber threats and incidents. The NIST CSF is based on industry standards and best practices, and it is a voluntary framework that organizations can adopt and tailor to their specific needs and risk profiles. It consists of three main components: Core: The Core is the heart of the framework and provides a set of cybersecurity activities and desired outcomes. It is organized into five key functions: Identify: This function involves understanding and managing cybersecurity risks by identifying critical assets, assessing vulnerabilities, and understanding the potential impact of cyber threats. Protect: The Protect function focuses on implementing safeguards to ensure the security and resilience of critical infrastructure. It includes activities such as access control, awareness training, data protection, and secure configurations. Detect: The Detect function involves continuous monitoring and timely detection of cybersecurity events. It includes activities such as threat intelligence, anomaly…
  - Find the right software solution for NIST CSF guidance by comparing software capabilities and covered guidance supported by the software. The NIST Cybersecurity Framework (CSF) 2.0 is a voluntary guidance document intended to assist organizations in managing and mitigating cybersecurity risks. The framework is specifically designed to help organizations, including critical infrastructure sectors, identify, protect, detect, respond to, and recover from cyber threats and incidents.
- NIST SP 800-53 (LOW)1. What is NIST SP800-53? The National Institute of Standards and Technology (NIST) Special Publication 800-53 (SP800-53) is a comprehensive cybersecurity framework that provides guidelines and controls for federal information systems and organizations. While it is not specifically focused on critical infrastructure, it serves as a valuable resource for enhancing cybersecurity practices in critical infrastructure sectors. NIST SP800-53 covers a wide range of security controls and best practices that organizations can implement to protect their information systems from various cyber threats. The framework is organized into 18 control families, each addressing a specific area of cybersecurity. Some of the key control families include: Access Control (AC): Controls related to granting and managing access to information systems and resources. This includes user identification, authentication, authorization, and accountability. Incident Response (IR): Controls focused on detecting, responding to, and recovering from cybersecurity incidents. It includes incident response planning, incident handling, and communication protocols. Configuration Management (CM): Controls related to establishing and maintaining secure configurations for information systems. This includes configuration baselines, change management processes, and configuration monitoring. System and Information Integrity (SI): Controls aimed at ensuring the integrity of information systems and data. This includes malware protection, security event monitoring, and vulnerability scanning.…
  - Select the appropriate software solution for NIST SP 800-53 (LOW) control baseline by comparing software capabilities and covered controls supported by the software. The NIST SP 800-53 (LOW: Low-Impact Systems) is a comprehensive cybersecurity framework that provides guidelines and controls for federal information systems and organizations. While it is not specifically focused on critical infrastructure, it serves as a valuable resource for enhancing cybersecurity practices in critical infrastructure sectors.
- NIST SSDF1. What is NIST SSDF? The NIST SSDF (Secure Software Development Framework) is a cybersecurity framework developed by the National Institute of Standards and Technology (NIST) to help organizations secure their software development processes. The framework provides guidelines and best practices to integrate security into every phase of the software development life cycle (SDLC), from design to deployment and maintenance. The NIST SSDF Framework consists of a set of core principles and practices aimed at ensuring the development of secure and resilient software. It emphasizes the importance of proactive security measures and risk management throughout the entire software development process. Key components of the NIST SSDF Framework include: Risk Assessment: The framework emphasizes the need for conducting risk assessments early in the software development life cycle. This involves identifying potential security risks and vulnerabilities and analyzing their potential impact on the software and the overall system. Security Requirements: The NIST SSDF Framework promotes the inclusion of security requirements in the software development process. These requirements are defined based on the identified risks and help guide the development team in implementing appropriate security controls. Secure Design: The framework emphasizes the importance of secure design principles in developing resilient software. This involves…
  - Choose the appropriate software solution for NIST SSDF practices by comparing software capabilities and covered practices supported by the software. The NIST SSDF (Secure Software Development Framework) is a cybersecurity framework developed by the NIST to help organizations secure their software development processes. The framework provides guidelines and best practices to integrate security into every phase of the software development life cycle (SDLC), from design to deployment and maintenance.
- Browse all
Services
- Compliance Services
  - PCI DSS
  - NERC CIP
  - NIST CSF
  - Evaluate your software’s capabilities that support PCI DSS compliance
  - Assess your software’s features that help organizations achieve NERC CIP compliance
  - Review your software’s features that align with NIST CSF best practices
  - NIST SSDF
  - ISO/IEC 27001
  - HIPAA
  - Evaluate your software’s features that help organizations meet NIST SSDF practices
  - Assess your software’s features supporting ISO/IEC 27001 compliance
  - Evaluate your software’s features that help organizations meet HIPAA compliance
  - Browse all
- Strategy and Risk
  - Strategy and Risk consulting services assist critical infrastructure organizations in identifying, assessing, and mitigating potential risks through a structured approach. This enables businesses to align cybersecurity with their objectives while safeguarding assets and reputation
- Cybersecurity for OT
  - Cybersecurity consulting services for OT known as Operational Technology (OT), focuses on safeguarding Industrial Control Systems (ICS) that oversee critical industrial processes. These systems, including SCADA, DCS, PLCs, HMIs, and sensors, are essential in various sectors, from power generation to manufacturing and transportation
Resources
- Latest News
  - Stay up to date with the latest cybersecurity regulations, standards, frameworks, and industry best practices.
- Blog
  - Receive updates and practical insights on the implementation of cybersecurity regulations, standards, requirements, frameworks, and best practices.
- Reports
  - Reports and research on emerging cybersecurity frameworks, guidelines, regulations, and industry best practices to provide a comprehensive understanding of the evolving cybersecurity landscape.
- Data Sheets
  - Learn how organizations improve compliance with cybersecurity regulations, standards, frameworks, and best practices through our services.
- White Papers
  - Access white papers on cybersecurity regulations, standards, requirements, frameworks, and best practices.
About
FAQ

Apozy Airlock

by Apozy

share

Scope assessment

Compliance evaluation

What is Apozy Airlock?

Apozy Airlock is a security platform that focuses on providing endpoint protection. It uses behavioral analysis and threat intelligence to detect and prevent advanced threats, including malware and ransomware. Apozy Airlock helps organizations strengthen their overall cybersecurity posture.

Cybersecurity Regulations, Standards and Frameworks Supported

HIPAA

ISO/IEC 27001

NERC CIP

PCI DSS

MITRE ATT&CK®

NIST CSF

NIST SP 800-53

NIST SSDF

Capabilities

Endpoint and Device Protection

Application whitelisting and blacklisting
Application whitelisting/blacklisting
Behavioral analysis and anomaly detection
Behavioral monitoring
Centralized management and policy enforcement
Compliance reporting and auditing capabilities
Data loss prevention (DLP)
Device control and USB port management
Endpoint compliance monitoring
Endpoint detection and response (EDR)
Endpoint encryption
Endpoint security agent deployment and updates
Host-based firewall
Incident response support
Integration with endpoint management systems
Mobile device management (MDM)
Patch management
Reporting and auditing
Secure boot and BIOS protection
Secure remote access and VPN support

SSDF Controls supported by the software

NIST SSDF_Prepare the Organization (PO) Implement Roles and Responsibilities (PO.2)

PO.2.2

NIST SSDF_Implement Supporting Toolchains (PO.3)

PO.3.1
PO.3.2
PO.3.3

NIST SSDF_Define and Use Criteria for Software Security Checks (PO.4)

PO.4.1
PO.4.2

NIST SSDF_Implement and Maintain Secure Environments for Software Development (PO.5)

PO.5.1
PO.5.2

NIST SSDF_Protect Software (PS) Protect All Forms of Code from Unauthorized Access and Tampering (PS.1)

PS.1.1

NIST SSDF_Provide a Mechanism for Verifying Software Release Integrity (PS.2)

PS.2.1

NIST SSDF_Archive and Protect Each Software Release (PS.3)

PS.3.1
PS.3.2

NIST SSDF_Produce Well-Secured Software (PW) Design Software to Meet Security Requirements and Mitigate Security Risks (PW.1)

PW.1.1
PW.1.2
PW.1.3

NIST SSDF_Review the Software Design to Verify Compliance with Security Requirements and Risk Information (PW.2)

PW.2.1

NIST SSDF_Reuse Existing, Well-Secured Software When Feasible Instead of Duplicating Functionality (PW.4)

PW.4.1
PW.4.2
PW.4.4

NIST SSDF_Create Source Code by Adhering to Secure Coding Practices (PW.5)

PW.5.1

NIST SSDF_Configure the Compilation, Interpreter, and Build Processes to Improve Executable Security (PW.6)

PW.6.1
PW.6.2

NIST SSDF_Review and/or Analyze Human-Readable Code to Identify Vulnerabilities and Verify Compliance with Security Requirements (PW.7)

PW.7.1
PW.7.2

NIST SSDF_Test Executable Code to Identify Vulnerabilities and Verify Compliance with Security Requirements (PW.8)

PW.8.1
PW.8.2

NIST SSDF_Configure Software to Have Secure Settings by Default (PW.9)

PW.9.1
PW.9.2

NIST SSDF_Respond to Vulnerabilities (RV) Identify and Confirm Vulnerabilities on an Ongoing Basis (RV.1)

RV.1.1
RV.1.2

NIST SSDF_Assess, Prioritize, and Remediate Vulnerabilities (RV.2)

RV.2.1
RV.2.2

NIST SSDF_Analyze Vulnerabilities to Identify Their Root Causes (RV.3)

RV.3.1
RV.3.2
RV.3.3
RV.3.4

Scope Impact

Periodic compliance activities supported by the Software

Automated generation of compliance status reports
Ensuring data privacy and protection measures are up to date.
Maintain compliance and evidence documentation
Monitor and address customers' compliance failures
Monitoring and documenting system changes for compliance impact
Ongoing evaluation and management of security risks.
Organizing periodic security awareness training for users
Periodic audits of user permissions and access rights.
Perform quarterly compliance process review
Regular updates to the incident response plan
Routine updates to fix vulnerabilities and maintain security standards
Testing backup and recovery plans to ensure operational

The Software store, process, or transmit

Customer account data
Sensitive information such a as Cardholder Data (CHD), Protected Health Information (PHI), Intellectual Property (IP), Bulk Electric System Critical Information (BCSI)
Other classified information as per relevant compliance standards
Not Applicable

The Software requires to be integrated with other systems impacting the cybersecurity or compliance of the customer

Required integration
Optional integration
Not Applicable

Software modules implemented

Modules that provide cybersecurity services for compliance (e.g., built-in features for PCI DSS, NERC CIP compliance, recurring activities, etc.)
Modules that securely store, process, or transmit customer account data or other sensitive information
Modules that facilitate network security controls
Modules that virtualize (e.g., machines, networks, appliances, applications, and hypervisors)
Modules purchased, subscribed (e.g., SaaS, bespoke and custom software, etc.)
Tools, code repositories, and systems that implement software configuration management or to systems that can impact the cybersecurity
Not Applicable

Software vendor Third-Party Service Providers (TPSPs) used

TPSPs that store, process, or transmit customer account data or other sensitive information on the entity’s behalf
TPSPs that impact the cybersecurity of the software vendor account data, sensitive information (e.g. vendors providing remote support)
TPSPs that manage software vendor modules/components included in the evaluation scope
Not Applicable

NIST SSDF scoping

Software secure development lifecycle

Prior to release, software and third-party components undergo thorough testing to identify and fix vulnerabilities
Any newly discovered vulnerabilities are addressed and resolved
The integrity of all software code, including third-party components, is maintained throughout the entire software lifecycle
Software releases and updates are securely delivered to guarantee the integrity of the code
Timely software updates are provided to customers to address known vulnerabilities
For hosted environment, the vendor takes responsibility for patching/updating the Software they provide
Not Applicable

The Software vendor provides support during installation or set-up

Yes
No
Not Applicable

The Software vendor provides an implementation guide to assist customers in securely setting up the application

Yes
No
Not Applicable

Alternatives

RevBits Endpoint Security

by RevBits

Next DLP

by Next DLP

Comodo Dragon Platform

by Comodo

Stay informed

Sign up to receive the latest news on cybersecurity regulations from Compliance Labs.

We promise not to spam you.

Email

Acceptance

I accept the terms and conditions.

By proceeding, you agree to our Terms of Use and Privacy Policy. You may unsubscribe at any time.

Tour Ariane – 5 place de la Pyramide
92088 Paris La Défense CEDEX

Contact us

Linkedin-in X-twitter

About
Why Compliance Labs
The team

services
Compliance Services
Strategy And Risk
Cybersecurity for OT

Resources
Resources
Blog

my account
Join us
Log in
Get listed (for Vendors)

FAQ
|
Terms of use
|
Privacy Policy

© 2024 Compliance Labs - All Rights Reserved.

Hide similarities
Highlight differences

Select the fields to be shown. Others will be hidden. Drag and drop to rearrange the order.

Software logo
Vendor
What is this Software?
Website
Cybersecurity Regulations, Standards and Guidelines Tested
Other Cybersecurity Regulations, Standards and Guidelines Supported
Deployment
Environment
Region
Industry
Capabilities
Application and DevOps Security
Asset Inventory and Management
Audit and Compliance Management
Awareness and Training
Backup and Recovery
Data Security
Endpoint and Device Protection
Identity Management and Access Control
Incident Response
Logging and Threat Detection
Network security
Posture and Vulnerability Management
Risk Assessment and Management
Software Bill Of Materials (SBOM)
Zero Trust Network Access
HIPAA Requirements Supported by the Software
MITRE Mitigations Enterprise Supported by the Software
ISO/IEC 27001 Requirements Supported by the Software
NERC CIP Requirements Supported by the Software
NIST CSF Controls Supported by the Software
NIST SP6800-53 (LOW) Controls Supported by the Software
NIST SSDF Controls Supported by the Software
PCI DSS Requirements Supported by the Software
Scoping
Periodic compliance activities supported by the Software
The Software store, process, or transmit
The Software requires to be integrated with other systems impacting the cybersecurity or compliance of the customer
Software modules implemented
Software vendor Third-Party Service Providers (TPSPs) used
Software NERC CIP scoping
Software NIST SSDF scoping
Software PCI DSS scoping

Compare

Compare ×

View comparison Continue browsing software