SMARTTILE · DEVICEAUTOMATE™ · SOPHOS FIREWALL · BETABETA

Sophos Firewall, from the box and from Sophos Central

BETA — built and unit-tested, switched off until proven on a real Sophos firewall. A read-only API administrator on the firewall and, optionally, a read-only Sophos Central credential give SmartTile the rule base with a change history, interfaces, IPsec configuration, administrator changes, identity, HA status and SFOS advisories.

SmartTile integrates with
Sophos Firewall (SFOS on XGS / XG, virtual or Home Edition) through its on-box XML API (/webconsole/APIController, admin port 4444) — and Sophos Central (Sophos Fusion) Firewall API with a tenant or partner credential.
How SmartTile automates it
Once switched on, SmartTile's agent reads each connected firewall every 5 minutes and its firewall + NAT rules hourly into a change ledger; it fills identity from Sophos Central, raises SFOS advisories, snapshots the configuration, logs administrator changes, and turns each new problem into one Workflow event.
Category
DeviceDeviceAutomate™

Sophos keeps half its story on the box and half in Sophos Central. SmartTile reads both doors, read-only: its XML client can only build Get requests, and the Central client never calls an upgrade, action or import. Central-managed firewalls get serial, model, SFOS version and HA from Central; every firewall with an API admin gets its rules and configuration. Beta: platform and company switches ship off.

What is built today

Rules + change ledger

Hourly, every firewall rule (zones, networks, services, action, web / IPS / app-control) and NAT rule. Each added, removed, changed or moved rule is logged; the first read is the baseline.

Interfaces, VLANs, IPsec

Every 5 minutes: interfaces and VLANs with zone, address and admin state; IPsec connections with type, remote host and subnets — as configured.

Administrator changes

Administrator accounts are compared every read: added, removed, or a new profile / status / login restriction. Shown in AccessAutomate (account changes, not sign-ins).

Configuration snapshot

Config Backups save rules, NAT, objects, interfaces, VPN, admins and services as one file with every secret removed; saved and diffed only on change. Not a restorable .bak.

Identity from Central

Serial, model, SFOS version and hostname written through the shared identity writer, matched by serial, public IP or hostname — only within the device's own company.

Central status + HA

Whether Sophos Central sees the firewall connected or suspended, and the HA cluster mode, status and peers.

SFOS advisories

From Central's firmware check: newest release on the running line, else the next line — never a multi-line jump. SmartTile never installs; it re-reads the version afterwards.

One Workflow per problem

“A Sophos firewall reports a problem” fires once when it opens: Central disconnected or suspended, HA fault, API unreadable, a new administrator, newer SFOS.

What it takes — on the firewall, and in Sophos Central

  1. Profile. Profiles → Device access → Add: e.g. “SmartTile read-only”, every area Read-only.
  2. Administrator. Authentication → Users → Add: type Administrator, that profile, a long random password.
  3. API access. Administration → API access (Backup & firmware → API on older SFOS): turn it on, add 157.245.117.9 under Allowed IP hosts, Apply.
  4. Reach. Administration → Device access: HTTPS for the zone SmartTile arrives from (from the internet, a Local service ACL exception for 157.245.117.9).
  5. Central (optional). central.sophos.com → Global Settings → API Credentials → Add credential with a read-only role; copy the client ID and secret into DeviceAutomate → Sophos Firewall.
Then Devices → the firewall → Sophos → Setup: username, password, Test, Save. Delete the administrator and access ends.
DoorWhat works
XML API (on-box admin)Rules + ledger, interfaces / VLANs, IPsec configuration, administrator changes, configuration snapshot.
Sophos Central — tenantIdentity, connected / suspended, HA, SFOS advisories. A company admin adds it for their company.
Sophos Central — partnerThe same for every managed tenant; SmartChoice super admins only, each tenant mapped to one company. Unmapped tenants are never read.
BothThe whole list. The on-box door works without Central, and the reverse.
SmartChoice · SmartTile DeviceAutomate™ — Sophos FirewallPage 1 of 2
SMARTTILE · DEVICEAUTOMATE™ · SOPHOS FIREWALL — EXACTLY WHAT SMARTTILE ASKS, AND HOW IT IS KEPT SAFE

Exactly what SmartTile calls

POST/webconsole/APIController (form field reqxml)one Get per entity — the client cannot build anything else
GetAdminSettings · Interface · VLAN · VPNIPSecConnection · User · HAConfigurationTest, health, IPsec, administrators
GetFirewallRule · NATRulerule inventory, hourly
GetZone · DNS · IPHost(Group) · FQDNHost · Services · ServiceGroup · LocalServiceACL · …configuration snapshot
POSTid.sophos.com/api/v2/oauth2/tokenCentral sign-in (client credentials)
GET/whoami/v1 · /partner/v1/tenantstenant or partner; managed tenants
GET{region}/firewall/v1/firewallsidentity, connection, HA
POST{region}/firewall/v1/firewalls/actions/firmware-upgrade-checkwhich upgrades Central offers — a read; schedules nothing

Security and control

Read-only by construction

The XML client only builds Get; the Central client calls no upgrade, action or import. SmartTile never changes, upgrades or reboots a firewall.

Encrypted, never shown

The admin password and Central client secret are sealed with AES-256-GCM and never returned — only “set”. Secret-named fields are stripped from everything read.

Password only to a pinned certificate

The XML API sends the password in every request, so it goes only in the POST body, only to the certificate trusted at Test (SHA-256 fingerprint) — checked before it is sent.

The company is the tenant

Platform and company switches default off. A Central firewall binds only to a device in its mapped company; every route checks the caller's company, and writes are admin-only and logged.

Built today vs. what Sophos's APIs do not give

AreaToday (beta)Not available
ProofUnit-tested against Sophos's docs and official SDK.Proven on a real firewall — then the platform switch goes on.
Up / downStays with SmartTile's ping / SNMP checks.The API poller never marks a firewall down or opens an outage ticket.
VPNIPsec connections as configured; listed in VPNAutomate as “state unknown”.Live tunnel up/down — not in the XML API, so tunnels never alert.
Backups / accessSecrets-removed configuration snapshot; administrator account changes.A restorable .bak; administrator sign-in events.
Firmware / healthSFOS advisories for Central-managed firewalls.Advisories without Central; CPU / memory over the API (use SNMP).

Common objections

ObjectionAnswer
“The XML API sends our admin password every time.”That is Sophos's design. Use a read-only profile, allow only 157.245.117.9, and SmartTile sends it only to the pinned certificate.
“Will it flood our IT Service Management (ITSM) system?”Nothing tickets by itself. A Workflow fires once per problem, and firmware ticketing follows the company's own FirmwareAutomate switch, off by default.
A read-only administrator on the firewall — and Sophos joins the pane your NOC already watches.
SmartChoice · smarttile.smartchoiceus.com · (800) 217-3096, 24×7 · verified 2026-10-06Page 2 of 2