Compliance Matrix.xlsx

XLSX spreadsheet 27 KB Posted

Attached to
DA10--VA-26-00029054 - Data Loss Prevention (DLP) Infrastructure Solution - New Requirement
Solicitation number
36C10B26Q0418
Issued by

About this file

This is a Compliance Matrix template for evaluating vendor responses to a Data Loss Prevention (DLP) Infrastructure Solution requirement for the Department of Veterans Affairs Technology Acquisition Center Austin (Solicitation Number: 36C10B26Q0418).

The matrix requires vendors to complete a comprehensive assessment across seven major capability categories by selecting "Meets," "Does Not Meet," or "Partially Meets" for each specification, with mandatory explanations for all responses. The seven evaluation categories are: (1) Data Discovery and Classification—25 requirements covering data discovery across various stores, sensitive data identification, custom classification rules, file analysis, labeling capabilities, and compliance with standards such as CCPA/CPRA, HIPAA, PCI DSS, and NIST; (2) Data Protection and Risk Reduction—28 requirements addressing security governance, access controls, permission mapping, data exposure identification, automated remediation, and customizable dashboards and reporting; (3) Misconfiguration Management—9 requirements for identifying and fixing misconfigurations in SaaS and IaaS platforms, workflow automation integration, and Active Directory assessments; (4) Third-Party Application Risk and Identity Security and Risk Management—7 requirements each for identifying external accounts, privileged users, anonymous access, and SIEM/SOAR integration; (5) Activity Monitoring and Threat Detection—23 requirements for monitoring data activity, detecting threats, generating alerts, MITRE ATT&ACK mapping, and incident response capabilities; (6) Data Access Governance—5 requirements for role-based access controls, just-in-time access, and self-service portals; (7) Data Lifecycle Automation, Architecture and Scalability, and Security and Compliance—covering automation of data migration, scalability specifications, FedRAMP Moderate authorization, and certifications in SOC 2, SOC 3, ISO, HIPAA, and NIAP Common Criteria.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Compliance Matrix Instructions: Please complete all sections of the Compliance Matrix highlighted in yellow.

1. Using the drop down arrow within Column C, select "Meets", "Does Not Meet" or "Partially Meets" for each Solution Requirement Specification identified in Column B.

2. Include an explanation within Column D for ALL responses (including Meets, Does Not Meet or Partially Meets).

CategoryMinimum Storage System SpecificationsComplianceExplanation
Section 1.1 - Product Requirements
Data Discovery and Classification1.The solution shall have the capability to discover and classify sensitive and regulated data.
2.The solution shall support the discovery and classification of data across various data stores. The vendor shall provide a list of supported data stores.
3.The solution shall be able to discover secrets and keys.
4.The solution shall have the ability to process large and increasing volumes of data in big data repositories.
5.The solution shall automatically update classification policies to reflect the latest rules and regulations.
6.The solution shall allow for the creation of custom classification rules.
7.The solution shall offer the ability to tune and reduce false-positives.
8.The solution shall provide customizable scan scoping.
9.The solution shall provide file analysis capabilities.
10.The solution shall use standard classification policies across different data stores.
11.The solution shall allow for the creation of custom rule-based classifiers.
12.The solution shall be able to scan various file types. The vendor shall provide a list of supported file types.
13.The solution shall support Optical Character Recognition (OCR) scanning.
14.The solution shall have defined procedures for performing classification scans. The vendor shall describe how the solution performs these scans.
15.The solution shall have the capability to automatically apply labels to data.
16.The solution shall allow for the creation of custom labels.
17.The solution shall monitor and report on labeling progress.
18.The solution shall accommodate and appropriately handle already labeled files.
19.The vendor shall describe whether the solution accesses or retains sensitive customer data.
20.The solution shall have a local collector.
21.The solution shall provide the ability to show the location of data within the environment.
22.The solution shall offer contextual search functions to understand factors such as file type, sensitivity, user type, location, and other metadata.
23.The solution shall have the ability to locate all detected information pertaining to a given person to ensure compliance with data privacy regulations.
24.The solution shall be able to create a data asset inventory and catalog.
25.The solution shall facilitate compliance and enable adherence to common industry regulatory standards such as CCPA/CPRA, HIPAA, PCI DSS, NIST, and others.
Data Protection and Risk Reduction1.The solution shall support data security governance processes including personally identifiable information (PI) and sensitive information (SI) data security, privacy auditing, and incident investigation.
2.The solution shall provide the ability to access controls, protection, archival, and disposal policies for sensitive data.
3.The solution shall have the capability to perform quarantine actions.
4.The solution shall be able to identify stale data.
5.The solution shall map granular permissions to data.
6.The solution shall normalize permissions across different platforms.
7.The solution shall identify and visualize data access paths, permissions, and potential exposure points.
8.The solution shall identify and report on unique permissions.
9.The solution shall clearly depict the roles assigned to users on each platform.
10.The solution shall identify data owners.
11.The solution shall enable data owners to control access to their data.
12.The solution shall identify publicly exposed sensitive data.
13.The solution shall identify data shared externally.
14.The solution shall provide recommended actionable insights for data protection and risk reduction.
15.The solution shall display sharing links in context with data sensitivity and staleness.
16.The solution shall identify stale permissions for each user.
17.The solution shall have the capability to automatically revoke organization-wide and public sharing links.
18.The solution shall automatically revoke external user access to sensitive data.
19.The solution shall automatically revoke stale permissions to data.
20.The solution shall provide customizable remediation policies.
21.The solution shall provide a graphical view of data exposure in the form of dashboards.
22.The solution shall offer customizable dashboards.
23.The solution shall provide compliance dashboards and reports.
24.The vendor shall describe other reports provided by the solution.
25.The solution shall allow for the creation of custom reports.
26.The vendor shall describe how the solution allows for the configuration and extension of reports within the tool and whether it extends reporting beyond the platform, indicating the most widely used reporting and data analytics by existing customers.
27.The solution shall allow for the export of reports.
28.The vendor shall offer data risk assessments.
Misconfiguration Management1.The solution shall have the capability to discover misconfigurations in Software as a Service (SaaS) applications.
2.The solution shall have the capability to automatically fix misconfigurations in both SaaS and Infrastructure as a Service (IaaS) platforms.
3.The solution shall be able to integrate with workflow automation tools.
4.The solution shall have the ability to integrate with incident management systems (e.g., ServiceNow, Jira) to create tickets.
5.The solution shall provide a timeline view of the cloud environment, enabling the detection of posture changes and tracking the evolution of the system over time.
6.The solution shall analyze single sign-on (SSO) states across all assessed platforms.
7.The vendor shall describe how the solution tracks multi-factor authentication (MFA) across all assessed platforms, including for each user.
8.The solution shall assist in finding and fixing Active Directory (AD) misconfigurations.
9.The solution shall have the capability to assess password expiry settings.
Third-Party Application Risk1.The solution shall have the capability to identify external and personal accounts with access to data.
2.The solution shall be able to identify anonymous user access.
3.The vendor shall describe how the solution identifies privileged users from external domains.
4.For user-related configurations, the solution shall enrich user settings data with relevant directory context (e.g., department, company).
5.The solution shall have the capability to identify privileged accounts.
6.The solution shall be able to integrate with Security Information and Event Management (SIEM) and Security Orchestration, Automation, and Response (SOAR) platforms.
7.The solution shall have the capability to identify stale group memberships.
Identity Security and Risk Management1.The solution shall have the capability to identify external and personal accounts with access to data.
2.The solution shall be able to identify anonymous user access.
3.The vendor shall describe how the solution identifies privileged users from external domains.
4.For user-related configurations, the solution shall enrich user settings data with relevant directory context (e.g., department, company).
5.The solution shall have the capability to identify privileged accounts.
6.The solution shall be able to integrate with Security Information and Event Management (SIEM) and Security Orchestration, Automation, and Response (SOAR) platforms.
7.The solution shall have the capability to identify stale group memberships.
Activity Monitoring and Threat Detection1.The solution shall monitor data activity.
2.The solution shall identify suspicious or risky file activity that may indicate a threat, such as users accessing or downloading unusual amounts of data.
3.The solution shall perform automated responses to stop an attack.
4.The solution shall detect and alert on abnormal activity.
5.The solution shall record a timestamp of activity.
6.The solution shall detect identity-based risks and threats, including privilege escalation.
7.The solution shall detect potential threats to the system, including misconfigurations, external threats, and insider threats.
8.The solution shall provide recommendations for mitigating identified risks.
9.The solution shall provide insight into attack methods.
10.The solution shall map alerts to MITRE ATT&CK tactics and techniques.
11.The solution shall allow for the generation of custom alerts.
12.The solution shall maintain a normalized and historical audit trail of events.
13.The vendor shall describe how the solution utilizes AI.
14.The solution shall monitor AI usage.
15.The vendor shall specify how often threat models are updated.
16.The solution shall be able to send alerts directly to the necessary personnel.
17.The vendor shall provide a list of Security Information and Event Management (SIEM) solutions that the solution integrates with.
18.The solution shall use webhooks, Syslog, APIs, or both to feed logs to SIEM solutions.
19.The vendor shall describe the process for exporting audit logs.
20.The solution shall provide an incident response team or services.
21.The solution shall be able to integrate with Security Orchestration, Automation, and Response (SOAR) platforms.
22.The solution shall provide exfiltration detection capabilities.
23.The solution shall provide endpoint monitoring capabilities.
Data Access Governance1.The solution shall enforce role-based access controls (RBAC) and Just-In-Time (JIT) access on data.
2.The solution shall have the capability to create custom review schedules and perform automated access reviews.
3.The solution shall provide a self-service portal for end-user access requests.
4.The solution shall manage permissions, monitor usage, and trigger remediation actions as necessary.
5.The solution shall integrate with existing agency workflows and tools.
Data Lifecycle Automation1.The solution shall automate the migration, removal, quarantining, and selective changes to data based on collected metadata and data set type.
2.The solution shall automatically reduce the blast radius and enforce least privilege on agency data sets.
3.The solution shall automatically optimize data storage based on usage and importance.
4.The solution shall automatically transfer data and stage data for migration.
Architecture and Scalability1.The vendor shall describe how the solution scales and handles unanticipated increases in data volume.
2.The vendor shall specify the solution’s limitations, including those related to data volume, performance bottlenecks, and strategies to mitigate them, as well as scalability to accommodate growing data volumes.
3.The vendor shall describe how the product optimizes resource usage.
4.The platform shall be architected in an efficient and secure way to limit sensitive data from leaving agency boundaries.
Security and Compliance1.The solution shall maintain FedRAMP Moderate authorization.
2.The solution shall be certified in the following compliance standards: SOC 2, SOC 3, ISO, HIPAA, and NIAP Common Criteria.

Sheet2

Meets
Does Not Meet
Partially Meets

File details come from the government source that posted it. Updated .