Set a web policy that preserves essential work
Fortra Secure Web Gateway is a cloud web-access and information-handling enquiry. The design should identify the users, applications and destinations that will pass through it. Do not confuse this offering with the separately named Fortra Web Gateway deployment discussion; confirm the current architecture and licence in the proposal.
Begin with acceptable-use requirements and the information that must not leave through supported web channels. Business applications, software updates and automated integrations can behave differently from ordinary browsing. A policy that works for a browser demonstration may still break a scheduled process or an essential supplier portal.
Test steering, inspection and user support together
Review supported traffic methods, identity integration and encrypted-session handling with the customer's security owner. Document what remains outside the proposed path. Use a representative pilot to test legitimate destinations, approved uploads and intentionally disallowed test activity. Where remote browser isolation or other optional functions are required, confirm their inclusion and compatibility rather than assuming a portfolio feature is licensed.
Establish the response to unavailable service and the authority for urgent exceptions. For UAE deployments, approve processing arrangements and any access to inspected information before rollout. Handover should contain policy categories, bypass decisions, device or user assignments and the way support investigates an incorrectly blocked site. Evaluate normal user experience as well as security events.
Evidence to request for this scope
- Confirm the offered SWG deployment, traffic-steering method and selected optional functions.
- Test business-critical websites, non-browser applications and supported upload controls.
- Record failure behaviour, exception approval and rollback for the pilot population.