DIRECT. PRIVATE. TRANSPARENT.
Security
Your infrastructure, your devices, your permissions.
A direct connection.
Monitoring data and administrative actions travel between your device and your Nagios installation over HTTPS. This access requires neither a NagWatch account nor a connector.
Credentials in Keychain
NagWatch stores username and password in each device’s Keychain. Server profiles hold a reference to these credentials. They do not sync through iCloud between iPhone and Mac.
HTTPS and certificates
The app validates the TLS connection. For a self-signed certificate or a private certificate authority, you can explicitly confirm one certificate per server after reviewing its issuer, validity and SHA-256 fingerprint.
A pin only applies to the exact, currently valid certificate you confirmed. If it changes, the new certificate must be confirmed again. There is no mode that accepts arbitrary certificates.
Your login determines permissions
Read and write access are handled separately. A successful login alone does not authorise administrative actions. Before sending, the app shows the affected server, host or service and the planned action.
On your LAN or over VPN
Your device must be able to reach the configured Nagios address. If Nagios is only accessible on your company network, use your existing VPN. The app does not create its own access to your network.
Notifications on Mac
The Mac app fetches data directly and generates notifications locally. It does not need a push relay. This applies while NagWatch is running and can reach the server.
Push is a later step
An optional connector and an encrypted push relay are planned for a future release. Nagios credentials are intended to remain exclusively on your devices. Administrative actions will continue to go directly to Nagios.