Heimdal
Heimdal offers a portfolio covering using name-resolution traffic as a security control point, keeping supported software and devices maintained and controlling elevated credentials and privileged sessions. The entries in this catalog include Heimdal DNS Security, Heimdal Patch and Asset Management and Heimdal Privileged Access Management. Heimdal DNS Security focuses on dns-layer threat blocking and traffic protection. Heimdal Patch and Asset Management focuses on endpoint patching and asset visibility. Heimdal Privileged Access Management focuses on endpoint privilege control and access administration. When reviewing Heimdal, compare the named products individually: a platform family, a specific module and a managed service can have different scopes and purchasing requirements. Selection should account for DNS routing, filtering policy, exceptions and the effect of protective decisions on legitimate applications. Portfolio detail - Heimdal DNS Security: the catalog lists Protective DNS filtering, Malicious domain blocking, Content category filtering. - Heimdal Patch and Asset Management: the catalog lists Automated patch deployment, Third-party application patching, Remote endpoint management. - Heimdal Privileged Access Management: the catalog lists Privileged credential vaulting, Just-in-time access, Least-privilege enforcement. For procurement, map each required capability to a named offering and confirm the edition, dependencies and delivery responsibility with the vendor. Product-level entries below provide the operational context and evaluation questions for that comparison.
Documented Software Products (3)
Heimdal DNS Security
Heimdal DNS Security from Heimdal focuses on DNS-layer threat blocking and traffic protection. It is DNS-layer protection technology used for using name-resolution traffic as a security control point. Capabilities - Protective DNS filtering: Uses DNS request handling as a control point for access to risky destinations. - Malicious domain blocking: Restricts access to domains that meet the configured threat or filtering rules. - Content category filtering: Applies filtering rules to the destination categories supported by the product. - DNS request visibility: Provides information about the DNS activity included in the deployment. - Threat intelligence support: Uses the documented threat information to inform DNS-based protection decisions. Use and operational context Heimdal DNS Security is relevant to organizations governing access to risky destinations when the requirement centers on using name-resolution traffic as a security control point. 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 DNS routing, filtering policy, exceptions and the effect of protective decisions on legitimate applications. 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? Heimdal DNS Security focuses on using name-resolution traffic as a security control point. - 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.
Heimdal Patch and Asset Management
Heimdal Patch and Asset Management from Heimdal focuses on endpoint patching and asset visibility. It is endpoint administration and patching technology used for keeping supported software and devices maintained. Capabilities - Automated patch deployment: Helps distribute software updates across the endpoints included in the management scope. - Third-party application patching: Brings supported nonoperating-system applications into the software update process. - Remote endpoint management: Supports administering devices without relying on an administrator being physically present. - Policy-driven automation: Turns repeatable endpoint administration tasks into configured management workflows. - Deployment scheduling: Supports planning when updates or management tasks should run. - Patch compliance reporting: Helps teams identify devices or software that still require update attention. - Software deployment: Distributes supported applications as part of the endpoint management workflow. Use and operational context Heimdal Patch and Asset Management is relevant to IT teams managing software updates across a device fleet when the requirement centers on keeping supported software and devices maintained. 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 Operating systems listed in the available documentation: Windows, macOS, Linux. Supported versions and feature coverage depend on the vendor support matrix.. Check version requirements and feature differences before rollout. Before adoption, review application coverage, deployment scheduling, restart behavior and a pilot group that represents production devices. 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? Heimdal Patch and Asset Management focuses on keeping supported software and devices maintained. - 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.
Heimdal Privileged Access Management
Heimdal Privileged Access Management from Heimdal focuses on endpoint privilege control and access administration. 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. - Just-in-time access: Limits privileged access to the period or approval conditions defined for a task. - Least-privilege enforcement: Restricts routine access so users and applications do not retain unnecessary elevated permissions. - Application privilege controls: Applies privilege decisions to application execution rather than granting unrestricted administrative rights. - Approval workflows: Routes access requests through the authorization process configured by the organization. Use and operational context Heimdal Privileged Access Management 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? Heimdal Privileged Access Management 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.