Network access controls restrict connections to the hosted application and help manage traffic between platform components and external systems. Public service endpoints sit in front of private application hosting, with access rules defining the permitted routes.
Network protection works alongside application authentication and permissions. A permitted connection still needs the credentials and authorisation required by the service or receiving system.
Limit direct access to application instances through private networking.
Use controlled public endpoints for the services users need to reach.
Review integration connectivity together with credentials and API permissions.
The managed platform uses a web application firewall to provide traffic visibility and configured request controls. Managed rule groups cover common application threats, suspicious IP activity, operating-system attack patterns and automated traffic.
Firewall metrics, request sampling and security logs help the team understand traffic and investigate unusual behaviour. Rules are configured according to the platform’s needs, alongside service-level bot protection and application checks.
Request visibility supports investigation of unwanted or unusual traffic.
Configured rules complement authentication and service validation.
Application and operational monitoring provide additional context for alerts.
Govform’s managed application runs in private cloud networks behind its public delivery and load-balancing endpoints. Application instances do not receive public IP addresses, helping limit direct exposure to the internet.
Network separation defines how application components, storage and connected services communicate. It complements library and service permissions, which control the actions people and integrations can perform once they reach an authorised endpoint.
Private application hosting separates instances from direct public access.
Network rules control permitted communication paths.
Dedicated deployment options can place the application within an agreed customer cloud boundary.
Cloud threat detection analyses platform activity for potential security concerns. Signals include infrastructure changes, network-related activity and relevant storage events, with configured malware-protection services for upload storage.
Findings give the team information for investigation and incident handling. Their significance is assessed with application records, operational metrics and the service context, so the response can focus on the affected resources and activity.
Threat findings support detection and investigation in the cloud environment.
Our remote-working policy requires protected home Wi-Fi and VPN use on untrusted Wi-Fi when accessing sensitive systems. These requirements help staff protect connections while working away from the office.
Device encryption, screen locking and secure storage also apply during remote work. Staff are required to handle information through approved systems and remain alert to unexpected sign-in requests or connection problems.
Home Wi-Fi must use WPA2 or WPA3 protection.
Use a VPN on untrusted Wi-Fi for sensitive-system access.
Keep devices secure and report suspected loss or compromise promptly.
The managed hosting configuration uses controlled outbound networking for connections to external services. Integration design determines the destinations your service needs, while credentials and receiving-system permissions define what it can do there.
Plan connectivity before a service goes live. Test the connection, authentication and failure handling in QA, and coordinate changes with the system owner when a destination or network requirement changes.
Identify the external services and endpoints the journey needs.
Keep test and live connections and credentials distinct.
Discuss special network or certificate requirements during integration planning.
