The FortiSASE idea, but run in infrastructure you or a chosen provider control, rather than in a shared public cloud.
It delivers the SASE stack as a locally deployed platform. An organization or trusted provider runs the service in chosen locations, keeping control of operations and data handling.
State systems may want central control and visibility across all facilities, while keeping that data in locations and with operators they choose.
- Keeps logs and traffic processing in chosen locations.
- Gives a state agency one policy across its sites.
- Supports stricter data-residency rules.
Check before you buy
This is likely a statewide-scale project, not a single-facility purchase.
- Local control of points of presence and logs.
- Tenant separation for multiple agencies.
- Same policy model as FortiSASE and FortiOS.
| Control | Priority | How this helps |
|---|---|---|
| SA-9External System Services | P2* | Local operation gives you more control over external service risk. |
| AC-17Remote Access | P1 | Controls and monitors remote access. |
| SC-8Transmission Confidentiality and Integrity | P2* | Encrypts traffic from remote devices. |
Local deployment can make it easier to meet data location and staffing rules, but you’ll need to document who has access.
Based on CJIS Security Policy v6.1. This product can support these controls but can’t satisfy them alone. How to read this table