Security of the BrynQ Agent

Security of the BrynQ Agent

📘 Setting up Factorial - Sage 100 France? Follow the complete step-by-step guide: Setup an automated data interface between Factorial and Sage.

This article is for IT and security administrators. It explains how the BrynQ Agent protects the connection between BrynQ and your local systems, and what BrynQ support can see.

Network

  • Outgoing connections only. The Agent connects outward to BrynQ (https://app.brynq.com, port 443) and to Cloudflare Tunnel (port 7844). No inbound firewall ports are opened. See Network settings of the BrynQ Agent.
  • Encrypted in transit. Traffic between BrynQ and your server runs through the encrypted tunnel. You don't need your own SSL certificate or reverse proxy.
  • Local only by default. The Agent itself listens on 127.0.0.1 (port 7070). The local admin dashboard (port 7071) only accepts requests made on the server itself (to 127.0.0.1, localhost or ::1) and is never exposed through the tunnel.
  • Only what you enable. Only the modules selected during installation are available. Requests to other modules are refused.

Authentication

  • Every request to the Agent must include the customer (domain header) and a valid token (Authorization: Bearer header). The Agent checks each request with BrynQ. A token only counts for this Agent's own customer. Requests without a valid customer and token combination are refused (401).
  • The BrynQ API token used during installation is scoped to exactly one customer. It is stored on the server in platform-auth.json, protected with Windows data protection (DPAPI, LocalMachine). The installer does not pass it on a command line inside the installation. When you install silently with /BRYNQ_API_TOKEN, the token is on the command line you type, so run it from a protected script. See The API token for the BrynQ Agent.
  • Rate limiting: each endpoint accepts at most 120 requests per minute, to protect your systems against abuse.

Credentials and logs

  • SQL credentials and other connection settings are stored only on your server, in C:\ProgramData\BrynQ\Agent\config. BrynQ does not send connection strings to the Agent.
  • The BrynQ folders are locked: the owner is Administrators; SYSTEM and Administrators have full control and other users can only read. The config folder can't be read by other users. The installation and automatic updates stop when one of BrynQ's folders, or a file in config, was created by another user (see Troubleshooting the BrynQ Agent).
  • Sensitive values (tokens, passwords, connection strings, Authorization headers) are removed from the log files before they are written. The setup logs mask the values of secret switches.
  • Logs rotate daily and are kept for 30 days by default.

Module limits

  • Files: only the allowed folders and file extensions can be used. A path outside them is refused (403). An upload over the maximum file size is refused (413).
  • REST: only the allowed URL patterns can be called (403 "Refused: …"). Every redirect is checked against them, and path tricks are refused.
  • SOAP: the certificate check is on. It can be turned off for a web service by unticking Verify SSL on the SOAP page.

What BrynQ support can see

Section 7 of the licence agreement describes what BrynQ support can access through the Agent.

  • Always: the Agent's log files and service definitions, the status of its services, connections and checks, its settings, basic facts about the server (such as the Windows version and language, free disk space and the clock), and with Sage the Sage import logs and the settings the Agent uses for Sage. Passwords, tokens and other secrets are never included. BrynQ uses this only to solve an issue you report, never to improve its software.
  • Advanced diagnostics, only with your consent: Windows and Microsoft Office log entries of the last 3 days about BrynQ and the applications it works with, the state and events of antivirus, other security products and application control, folder permissions, and system settings such as proxy, firewall and PowerShell settings. BrynQ collects these only when the logs, status and settings are not enough.
  • Every access is recorded and shown to you.
  • The installer asks for consent on the Additional options page: Share advanced diagnostics (recommended). What does BrynQ support see? opens the overview.
  • You can change it any time on the admin dashboard: Troubleshooting › Advanced diagnostics. With the switch off, BrynQ support can't collect these details. You can still collect them yourself with Collect myself and decide whether to share them.
  • A re-install shows the current choice. A silent install or automatic update keeps it, unless you use /DIAGNOSTICS=1 or /DIAGNOSTICS=0. A new silent install without the switch has advanced diagnostics off.
  • The choice is stored in C:\ProgramData\BrynQ\Agent\config\diagnostics.json.
  • Click Support accesses on the Troubleshooting page to see each access by BrynQ support: when, what, and from which IP address.

Accesses by BrynQ support

Signed software and updates

  • The installer, the Agent, the service wrappers, the PowerShell scripts and the uninstaller are all signed with Microsoft Artifact Signing. The publisher shown by Windows is Salure ICT BV, BrynQ's legal entity.
  • Automatic updates are signed installers from BrynQ. The Agent checks the SHA-256 checksum before it runs an update, and refuses any file that is not a BrynQ Agent installer.

Verify the installer

Run this in PowerShell, with the path to the downloaded file:

$Installer = "C:\Users\Administrator\Downloads\brynq-agent-installer-<version>.exe"
$Signature = Get-AuthenticodeSignature -FilePath $Installer
$Signature | Format-List Status,StatusMessage,SignerCertificate,TimeStamperCertificate
Get-FileHash -Algorithm SHA256 -Path $Installer

Expected: status Valid, signer CN=Salure ICT BV, a timestamp certificate, and a SHA-256 hash that matches the Checksum on the BrynQ Agent page. Stop and contact BrynQ support if any check fails.

ℹ Allowlisting (App Control / WDAC, AppLocker)? The signing certificates are short-lived, so don't allow the Agent by certificate thumbprint. Use BrynQ's durable Artifact Signing identity instead (EKU 1.3.6.1.4.1.311.97.660267593.867465077.727055656.745229941), scoped to the BrynQ Agent files. This keeps working for automatic updates.