Documented Products & Services
Search and filter enterprise cybersecurity solutions by category, deployment architecture, supported operating systems, and verified pricing models. Default sorting is alphabetical.
Official leaderboards evaluated by technical benchmarks & scope...
Joe Sandbox
Joe Sandbox from Joe Security focuses on malware execution analysis and behavioral investigation. It is malware analysis technology used for examining suspicious files or observed execution behavior. Capabilities - Behavioral malware analysis: Observes how a suspicious file or sample behaves during the documented analysis process. - Static file analysis: Examines file characteristics without relying only on execution behavior. - Threat indicator extraction: Produces indicators that can inform investigation or be used in supported security workflows. - Analysis reporting: Organizes analysis results so analysts can review the observed behavior and threat assessment. - Analysis automation: Connects analysis with the automation or integration mechanisms supplied by the vendor. - Interactive investigation: Allows analysts to interact with the analysis session within the product's documented environment. Use and operational context Joe Sandbox is relevant to analysts triaging samples and investigating threats when the requirement centers on examining suspicious files or observed execution behavior. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review supported samples, analysis visibility, submission privacy and how findings are reviewed before operational decisions. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Joe Sandbox focuses on examining suspicious files or observed execution behavior. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
JumpCloud Directory Platform
JumpCloud Directory Platform from JumpCloud focuses on cloud directory management and device identity controls. It is identity and access management technology used for authentication, access policy or identity lifecycle administration. Capabilities - Cloud directory administration: Connects the documented identity and device administration functions through a cloud directory model. - Single sign-on: Centralizes application authentication so users can access assigned services through a consistent sign-in process. - Multifactor authentication: Adds another authentication factor to reduce dependence on passwords alone. - Conditional access: Applies access rules using conditions such as the user, device or session context. - Identity lifecycle management: Supports managing identity access as people join, change roles or leave an organization. - Federated authentication: Supports connecting application authentication to external identity providers or federation protocols. - Passwordless authentication: Offers an authentication approach that reduces or removes the need to enter a password. - Directory integration: Connects identity administration or authentication with directory systems named in the documentation. Use and operational context JumpCloud Directory Platform is relevant to identity teams connecting users and applications when the requirement centers on authentication, access policy or identity lifecycle administration. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS. Before adoption, review supported identity providers, application connectors, access-policy design and the account lifecycle workflow. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? JumpCloud Directory Platform focuses on authentication, access policy or identity lifecycle administration. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
K7 Endpoint Security
K7 Endpoint Security from K7 Security focuses on business endpoint malware prevention and protection. It is endpoint security software used for endpoint protection and incident investigation. Capabilities - Ransomware protection: Addresses ransomware-related execution patterns or recovery controls described in the product documentation. - Device control: Provides policy controls for peripheral devices and removable media. - Malware prevention: Provides controls intended to detect or block malicious files and execution. Use and operational context K7 Endpoint Security is relevant to security teams administering employee devices or servers when the requirement centers on endpoint protection and incident investigation. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review agent compatibility, policy tuning, alert investigation and the response actions available in the selected edition. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? K7 Endpoint Security focuses on endpoint protection and incident investigation. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Keeper Enterprise
Keeper Enterprise from Keeper Security focuses on business password management and credential sharing. It is business password management technology used for organizing access to shared or individual credentials. Capabilities - Encrypted password vaults: Stores credentials within the protected vault model described by the vendor. - Secure credential sharing: Lets authorized users collaborate on credentials through the product's access controls. - Administrative policies: Gives organizations controls for governing how the password manager is used. - Password generation: Helps users create passwords without relying on manually chosen patterns. - Access reporting: Provides visibility into the administrative or credential activity included in the product. - Directory or identity integration: Connects organizational identity processes with password manager deployment or account administration. - Credential risk assessment: Highlights credential exposures or hygiene issues documented by the vendor. Use and operational context Keeper Enterprise provides an organizational password and credential-management workflow. Review the enterprise's vault and sharing structure, administrator permissions and identity lifecycle requirements, including how access is handled when a team member's role changes. Deployment and evaluation Before adoption, review vault permissions, account recovery, identity integration and a controlled onboarding and offboarding process. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Keeper Enterprise focuses on organizing access to shared or individual credentials. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Keeper Secrets Manager
Keeper Secrets Manager from Keeper Security focuses on application secret storage and access control. It is application secrets management technology used for controlling how software obtains and uses credentials. Capabilities - Application secret storage: Provides a controlled storage and access workflow for application credentials and other secrets. - Secret rotation: Supports changing secrets according to the credential lifecycle controls described by the vendor. - Developer and pipeline integration: Connects secrets access with the development or delivery tools supported by the product. - Fine-grained access policy: Controls which identities or workloads can access a given secret. - Secrets auditing: Provides records for reviewing access to protected secrets. Use and operational context Keeper Secrets Manager addresses programmatic access to protected application credentials. Evaluate how a workload obtains a secret, how its access is approved and recorded, and how the organization manages a secret change without interrupting dependent services. Deployment and evaluation Before adoption, review secret retrieval, access policy, rotation behavior and the consequences of a service or network interruption. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Keeper Secrets Manager focuses on controlling how software obtains and uses credentials. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
KeeperPAM
KeeperPAM from Keeper Security focuses on privileged access and session management. It is privileged access management technology used for controlling elevated credentials and privileged sessions. Capabilities - Privileged credential vaulting: Stores privileged credentials under centrally administered access controls. - Credential rotation: Supports changing privileged credentials to reduce the exposure associated with long-lived passwords. Use and operational context KeeperPAM is relevant to administrators governing access to sensitive systems when the requirement centers on controlling elevated credentials and privileged sessions. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review credential onboarding, access approvals, session controls and the operational impact of least-privilege policies. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? KeeperPAM focuses on controlling elevated credentials and privileged sessions. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Keyfactor Command
Keyfactor Command from Keyfactor focuses on certificate inventory and lifecycle management. It is cryptographic key or certificate technology used for managing protected keys, certificates or signing operations. Capabilities - Certificate inventory governance: Brings certificate discovery and lifecycle information into a centrally administered inventory. - Certificate lifecycle management: Coordinates certificate discovery, issuance, renewal or retirement within the documented management scope. - Certificate discovery: Builds visibility into certificates or cryptographic assets before lifecycle policies are applied. - Cryptographic key protection: Provides the documented protections for keys used in cryptographic operations. - Public key infrastructure services: Supports certificate issuance and trust infrastructure within the vendor's product scope. - Code signing workflows: Supports signing software or artifacts using the product's documented key access and policy model. - Certificate automation: Helps reduce repetitive certificate handling through the automation mechanisms described by the vendor. - Signing policy controls: Applies controls to how signing operations or protected keys can be used. Use and operational context Keyfactor Command is relevant to teams operating cryptographic trust services when the requirement centers on managing protected keys, certificates or signing operations. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Deployment: Cloud service / SaaS; Self-managed / on-premises option documented by the vendor. Before adoption, review key ownership, certificate discovery, integration requirements and recovery procedures for critical trust infrastructure. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Keyfactor Command focuses on managing protected keys, certificates or signing operations. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
KnowBe4 Security Awareness Training
KnowBe4 Security Awareness Training from KnowBe4 focuses on employee security education and phishing simulation. It is security awareness technology or service used for improving how employees recognize and handle security risks. Capabilities - Phishing simulations: Creates controlled exercises to assess how users handle realistic phishing scenarios. - Security training content: Provides learning material intended to improve security knowledge and decision-making. - Adaptive learning: Adjusts the training experience using the learner context described by the product. - User risk insights: Helps teams understand which user behaviors or exposures deserve additional attention. - Program reporting: Provides information for monitoring participation, outcomes and the progress of the awareness program. - Security coaching: Connects security learning with user behavior or the moment at which guidance is needed. - Employee threat reporting: Makes it easier for employees to escalate suspected phishing messages to the security team. Use and operational context KnowBe4's awareness platform combines a training program with controlled phishing exercises. Assess the content relevant to the employee population, the way campaigns are administered and how reporting is used to plan targeted learning or process improvements. Deployment and evaluation Before adoption, review training relevance, simulation design, reporting methods and the treatment of employee information. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? KnowBe4 Security Awareness Training focuses on improving how employees recognize and handle security risks. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.
Kroll Incident Response
Kroll Incident Response is a professional security engagement offered by Kroll. The service focuses on cyber incident investigation and containment. Capabilities - Incident investigation: Establishes what happened by examining relevant evidence and the scope of the incident. - Containment planning: Helps define steps intended to reduce an incident's immediate spread or effect. - Digital evidence analysis: Examines digital artifacts to support understanding the incident and its timeline. - Recovery assistance: Assists with the recovery tasks included in the engagement and agreed response plan. - Incident readiness services: Supports preparing for incidents before an emergency response engagement is required. - Root-cause assessment: Helps identify the factors associated with the incident so remediation can address the underlying exposure. Use and operational context Kroll's incident response entry addresses the investigation and handling of a cyber incident. Agree the business systems and evidence in scope, the decision-makers involved in containment and the communications needed to coordinate investigation with the recovery effort. Deployment and evaluation Deployment: Professional service delivered within an agreed engagement scope. Before adoption, review engagement scope, evidence handling, response authority and the responsibilities of internal and external responders. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Kroll Incident Response focuses on investigating and managing cybersecurity incidents. - What should a proof of concept establish? Test the listed capabilities against representative service deliverables, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.