Specifications & Constraints
This page serves as a unified reference for Keep Aware platform specifications, browser compatibility, known constraints, and current issues.
Infrastructure
In production deployments, exceptions may need to be made in other security solutions for Keep Aware infrastructure.
| Name | Resource | Purpose |
|---|---|---|
| Core domain | awarefilter.com | Used for extensions and clients to communicate with your Keep Aware tenant, retrieve policies, and enrich site activity |
| Sink domain | awarefilter.net | Used as a fallback for certain status connections |
| Logging IP address | 52.89.186.180 | Used for outbound logging to SIEM, SOAR and other tooling |
Versioning
Keep Aware deploys across several operating systems and browsers. The latest version and compatibility notes are stored below.
Client
Keep Aware is generally available for Windows, macOS, and Linux operating systems. Latest client downloads and versions are available on the Downloads page.
Browsers
Keep Aware deploys to several browser types and many Chromium-based browser variants. While there are browsers outside of this list with production deployments, we regularly test and maintain compatibility notes on the browsers listed below.
Google Chrome | 3.1.1 | Extension ID: camnmdjjfkcplbdlofbndmkmnfeegjoi Public Listing: Chrome Web Store | |
Microsoft Edge | 3.1.1, 3.1.1 | Recommended Extension ID: camnmdjjfkcplbdlofbndmkmnfeegjoi Public Listing: Chrome Web Store Extension ID: kkfcchpefnjflmleimpbklpcikdpbmcp Public Listing: Edge Addons | See Application bypass |
Mozilla Firefox | 3.1.1 | Extension ID: {f61bd1c4-311f-43c3-913f-13b7b37dc144}Public Listing: Firefox Addons | See Extension management |
Brave | 3.1.1 | Extension ID: camnmdjjfkcplbdlofbndmkmnfeegjoi Public Listing: Chrome Web Store | |
Arc | 3.1.1 | Extension ID: camnmdjjfkcplbdlofbndmkmnfeegjoi Public Listing: Chrome Web Store | See Windows policy |
Vivaldi | 3.1.1 | Extension ID: camnmdjjfkcplbdlofbndmkmnfeegjoi Public Listing: Chrome Web Store | |
Chromium | 3.1.1 | Extension ID: camnmdjjfkcplbdlofbndmkmnfeegjoi Public Listing: Chrome Web Store | |
Perplexity Comet | 3.1.1 | Extension ID: camnmdjjfkcplbdlofbndmkmnfeegjoi Public Listing: Chrome Web Store | See Chromium policy distribution |
ChatGPT Atlas | 3.1.1 | Extension ID: camnmdjjfkcplbdlofbndmkmnfeegjoi Public Listing: Chrome Web Store | See Chromium policy distribution |
Dia | 3.1.1 | Extension ID: camnmdjjfkcplbdlofbndmkmnfeegjoi Public Listing: Chrome Web Store | See Chromium policy distribution |
Safari | 3.1.1, 3.1.1 | Safari for MacOS App: Keep Aware Workspace Public Listing: App Store Safari for iOS Extension: Keep Aware Public Listing: App Store | See Deployment, Downloads, Extension management |
Knack | 2.0.14 | Knack for iOS App: Knack: Secure Browser Public Listing: App Store | |
Keep Aware (Hosted) | 3.1.1 | Extension ID: oelipjlpgoppkmhbjfgpomlbadkjddokUpdate URL: https://publishing.awarefilter.com/updates.xml | Most Chromium-based browsers support distribution directly through Keep Aware publishing servers. See Hosted distributions |
Performance & resource footprint
Keep Aware is designed to operate as a lightweight, low-overhead security layer that minimizes impact on browser and system performance, even under stress.
Browser performance impact
-
Under maximum benchmark pressure (e.g., BrowserBench) with all advanced features enabled—including selectors, dictionaries, and full policy evaluation, Keep Aware consumes approximately 8% of the browser's available processing capacity.
-
Under normal day-to-day usage, Keep Aware typically operates within 1–3% of the browser's total execution capacity, remaining effectively unnoticeable to users.
Resource utilization (browser extension)
| Resource | Usage |
|---|---|
| Memory / RAM | ~50–60 MB of browser memory |
| Storage / Disk | < 50 MB |
Client component footprint
When the optional desktop client is installed:
- Additional storage usage: ~100 MB
- Runtime impact: negligible
The client runs no continuous high-load background processes. Its activity is:
-
Periodic and lightweight, limited to:
- Fetching configuration updates
- Health-check pings
- Secure communication with the browser extension for file hashing and integrity checks
-
Idle by default, activating only when required by policy or extension requests
Design principle
Keep Aware prioritizes predictable performance, bounded resource usage, and user transparency, ensuring enterprise-grade protection without degrading browser responsiveness or system stability.
Installation method
Keep Aware aims to be extension-first. Any feature development is first fully exhausted using an extension-only approach. While we consider Keep Aware's extension fully functional, security teams often add the Keep Aware client as a on-device utility. This utility creates a shared memory space across browsers, further supports user-linking, and provides browser status updates for inactive browsers.
| Feature | Keep Aware extension | Keep Aware client |
|---|---|---|
| Events --- Structured browser based telemetry for page visits, login attempts, uploads, downloads, sensitive copy/paste, and inputs | ✅ | ✅ |
| Patterns --- Evaluate detection patterns across events and enforce policy across different browser-based activity | ✅ | ✅ |
| Account Selectors --- Link web application activity to "acting" user account | ✅ | ✅ |
| User Linking --- Link browser activity to SaaS users and company email addresses | ✅ | ✅ --- Supports quicker user linking across browsers. Browsers can share user-link information across the client to browsers that are not heavily used |
| Local User Linking --- Link browser activity to local machine user account | ❌ | ✅ |
| Device Information --- Fully link browsers to devices and enrich browser activity with IP Address, Hostname, MAC Address, and Device UUID | 🟨 --- Can be obtained through pushing out scripts via MDM | ✅ |
| Device Status --- Share overall browser deployment health per device | ❌ | ✅ |
| Extension Removal --- Capability to prevent users from uninstalling Keep Aware | 🟨 --- Force installed extensions are configured through MDM | ✅ --- Background service to regularly check on deployed extensions |
| Other common notes and roadmap | Keep Aware extension | Keep Aware client |
|---|---|---|
| Offline Patterns | To be supported for non-rarity-based patterns | |
| Offline Content Policy | To be supported for content categories, content policy | |
| App-Extension Blocking --- Safari equivalent of Extension management | To be supported. Will Keep Aware client deployment or DDM policy integration. |
Compatibility notes
Deployment
- Safari: Safari extensions must be installed through an Apple App Store application. Keep Aware can be installed as an application for this purpose through an MDM. Apple supports configuring Safari extension settings for devices enrolled in a mobile device management (MDM) solution, Apple Notes on Safari Extension Configuration. Each MDM vendor implements these settings differently. To learn how various Safari extensions management settings are applied to your devices and users, consult your MDM vendor's documentation.
Extension management
- Enforcement model: Keep Aware disables blocked extensions from inside the browser after they install; it does not prevent the installation itself.
- Re-enabling: Moving an extension from a block list to an allow list does not automatically re-enable it. Users must re-enable the extension in their browser, or reinstall it if it was uninstalled.
- Safari: Safari extensions must be installed through an Apple App Store application. Due to this, Safari applications get deployed to the macOS operating system and are treated similar to desktop applications. Cataloging and controlling Safari web extensions and applications through the Keep Aware client is planned. See App-Extension Blocking for status.
- Knack: Extensions and extension marketplaces are not allowed on mobile Chromium browsers.
Application bypass
- Edge: As of December 2025, Microsoft Edge browsers prevent any extension injection into Microsoft Copilot directly. The limitation is indepedent of Keep Aware and currently experience by browser security and dedicated enterprise browser vendors and is being tracked by the Edge Extensions team. Keep Aware continues to support application blocking and policy notices for Microsoft Copilot with full capability available in Chrome and other browsers.
Experimental access
- Knack: The Knack secure mobile browser is available as a preview to participating organizations.
Downloads
- Safari: As of February 2026, the downloads API is not yet supported by Safari. Apple has been adopting MV3 extension standards over the last two quarters and is expected to implement download monitoring.
- Firefox: As of February 2026, There is a known bug for pausing downloads of certain mime types. As a workaround, Keep Aware allows paused downloads until they are cancelled by the user. This has been raised to the Firefox development team. In the meantime, clients who want to block downloads should consider a "Restrict" safeguard.
- Knack: Download visibility and policy support expected in Q2 2025.
Hosted distributions
Keep Aware maintains a version of our extension through our own publishing servers. Typically these distribution receives updates 24-48 hours before the other publishing services. Discuss with your Keep Aware Technical Representative if you should be using this distribution. It may make sense in highly controlled domain-joined environments.
Windows policy
Newer browsers are in the process of gaining support for locked deployments through Windows environments:
- Arc: Arc browser development team expects support in early 2025.
Chromium policy distribution
Newer browsers often do not create their own registry or managed preference locations until they start to build more enterprise-facing features. Some settings on these browsers will point to "Chromium" generic configuration locations. Ex: Configuring Keep Aware settings for Chromium may also configure browsers like Comet.
Feature support
- Production: Most features are in production-use. Production use have been tested and are developed for every-day use.
- Customer Beta: We've released the feature to most environments for use alongside production workflows. We are quickly iterating on these features and they may not perform as expected.
- Experimental: We have a select few clients that we are working closely with to test and iterate on these features. The are not guaranteed to work in production settings and could potentially be removed from the product.
Known issues
This section outlines known bugs and issues currently affecting the product. Refer to this section for updates as we work to resolve these issues.
Current issues
Text cannot be copied from the Console (Medium)
- Description: Users are unable to highlight and copy any text displayed within the console, such as descriptions or other information presented as text. This issue occurs across all browsers and platforms, preventing users from copying text for external use.
- Impact: This affects the ability to quickly copy and share information displayed in the console, potentially causing frustration for users needing to reference or transfer the information.
- Status: This issue is considered largely resolved; if you encounter any trouble, please let us know.
Severity definitions
| Severity | Criteria | Examples | Remediation |
|---|---|---|---|
| Urgent | Defect causes the Product to be unusable. This issue prevents the extension from properly monitoring activities or the console from loading data properly. No workarounds are available. | - A complete loss of service - Real or perceived lack of data making an essential part of the Console unusable - Failure of a Sensor to monitor activities/traffic | Immediate Upon Solution |
| High | Defect causes major features or functionality to fail, resulting in a severe restriction of Product functions. A workaround is deemed to be unacceptable. | - Functionality is affected, but can be circumvented - Certain functions are disabled, but software remains operable | Immediate Upon Solution |
| Medium | Defect causes the feature to not meet planned requirements, resulting in minimal operational disruption. A workaround is available and the use of the Product can continue. | - Attributes or fields missing from an Event Search - Search result filters not fully functioning | Prioritized within Monthly Updates |
| Low | Defect causes almost no impact to functionality, resulting in limited business impact. | - Spelling issue or formatting - Loss of function of an Experimental feature | Next release |