Colt SSE
Control application access, including outside the office.
Security Service Edge (SSE) applies cloud-delivered security controls. It suits distributed users; review identities, devices and the applications they need.
SSE depends on identity, endpoints, supported applications, inspection and privacy requirements.
Let’s talk
How it works
Protect application access even when users are away from the office.
User and device
Identity and SSE policy
Authorised applicationAccess based on identity and context
Colt SSE with Zscaler integrates cloud access and inspection. Define user needs, public versus private applications and contracted controls.
Identity, device posture and permissions must fit the directory and applications. Zero Trust is not whole-network access after one login.
User and device
Identity and SSE policy
Authorised applicationSee why a flow is not working
A denial may stem from identity, policy, inspection or connectivity. Correlate logs with user and application before changing a rule.
Define justified exclusions, data handling and impact on sensitive applications. Data-loss prevention features depend on the package.
User and device
Identity and SSE policy
Authorised applicationContinuity without unrestricted access
Availability also depends on Internet, identity and private-application connectors. Test dependencies and recovery for the selected architecture.
Emergency procedures must preserve permissions and traceability. Disabling inspection or authentication is not an assumed acceptable fallback.
Illustrative case: from situation to decision
- Situation
- An external collaborator needs a private application from an authorised device.
- Option
- Define identity, device context and access limited to that application.
- Check
- Test permitted access, denial with unauthorised context and permission removal.
SSE provides security controls; it does not replace access links or select paths like SD-WAN.
Decisions for your project
- Identities
- Directory, authentication, devices and user groups.
- Applications and data
- SaaS, private services, inspection, exceptions and data residency.
- Dependencies
- Connectors, Internet, identity and incident response.
From design to operation
Pilot representative users and applications before extending policies, testing permitted and denied access.
Complements, alternatives and variants
Product sources
What challenge would you like to solve?
Tell us what is happening and what needs to change. You do not need to know the catalogue.
What happens next?
- Understand the context
What’s changing, where your teams work and what cannot fail. Still defining the brief? We can help structure it.
- Design the options
Bring needs, Colt capabilities and technical criteria together. Compare alternatives and explain dependencies and limits.
- Validate before committing
Coverage, feasibility, responsibilities and terms. A commercial proposal is developed with the relevant specialists.
ColtPlatinum guides the project and coordinates commercial discussions and follow-up. Colt validates feasibility, enters into the service contract, and provisions, installs and delivers the services.
Availability, coverage, capabilities, SLAs and timelines are subject to technical validation and contract. No diagram is a service guarantee.