Help Net Security launches Byoky across browsers and mobile platforms

Key points

• Help Net Security released Byoky for Chrome, Firefox, iOS, and Android.
• The product handles cryptographic key storage and access requests.
• No CVE was assigned; severity is assessed as medium.
• Admins should review extension and app policies plus key-handling controls.

Help Net Security has announced Byoky, a new product delivered through browser add-ons for Chrome and Firefox and through mobile clients for iOS and Android. The launch covers four client surfaces and centers on two functions: storing cryptographic keys and processing access requests. No CVE identifiers accompany the release, and the severity is assessed as medium.

Organizations using managed browsers or mobile device fleets may see Byoky appear in extension inventories and app catalogs. Because the product touches key material and access workflows, its footprint matters to identity and endpoint teams even without a vulnerability. The absence of a CVE does not mean no risk; it means the current concern is architectural and operational.

Key storage and access request handling are sensitive by nature. If keys are held in browser extensions or mobile apps, administrators need clarity on where keys reside, how they are protected, and whether access requests are logged and approved consistently. The multi-platform scope increases the number of places to monitor.

Product launches in the access and key-management space often precede policy updates. Watch for extension permissions, mobile app entitlements, and any admin console controls. Review whether Byoky is allowed by existing browser and app policies, and whether its access-request flow integrates with current identity providers.

What to do now

1. Inventory Byoky extensions and mobile apps across managed endpoints and app catalogs.
2. Review requested permissions and entitlements; block unapproved installs through policy.
3. Confirm where cryptographic keys are stored and how they are protected at rest and in transit.
4. Validate that access requests are logged, approved, and integrated with the identity provider.
5. Add Byoky to extension and app monitoring, allowlisting, and change-review workflows.
6. Instruct users to install only through approved channels and report unsolicited prompts.
7. Reassess severity if vendor documentation reveals additional key-handling or access-control details.

Original source

Help Net Security