Example policy. Dependencies and enforcement methods are agreed per project.
Access with a purpose
Let the application through. Keep the policy clear.
Your app needs sign-in, APIs and supporting content. Make those dependencies visible, then define what the service should do with traffic outside the policy.
Permitted service trafficOutside the policy
Your app
Access policy
Sign-inApp API / CDNOther traffic
The opportunity
A simple offer. A complete operation.
Application access for a practical retail workflow.
An app rarely depends on a single domain. Authentication, APIs, content delivery, notifications and payment services may each use separate infrastructure. Useful application whitelisting starts with understanding that dependency map.
Designed around the use case
What you can put to work.
01
An allowlist with a purpose
Create an access policy for the endpoints required by a business application, POS workflow or sponsored service. Decide what should happen when traffic falls outside the policy.
02
Product and traffic rules together
Relate supported access policies to the subscriber and charging setup. Keep the difference between permitted traffic, included data and chargeable usage explicit in customer communications.
03
A policy that stays maintainable
Validate third-party dependencies, domain changes, encryption behaviour and device traffic. Establish an update and regression process so app releases do not unexpectedly block a required service.
From idea to operation
A clear way in.
Start with the customer need. Agree the setup. Test the complete service journey.
01
Map the application
Identify owned and third-party endpoints, login and background service requirements.
02
Configure the policy
Agree supported identification methods and permitted traffic rules.
03
Validate and maintain
Test real devices, out-of-policy traffic and application updates before rollout.
Complete underneath
Simple to introduce. Serious about the systems.
Commercial, service and network capabilities work together. Explore the modules behind this use case and the responsibilities they cover.
Can encrypted traffic always be identified by app?
Shared infrastructure, encrypted DNS and VPNs affect traffic identification. We assess the available policy methods against your application’s endpoints and network behaviour.
Does an allowlist guarantee application security?
An allowlist controls network access. Application security, identity verification and payment protection each require their own controls.
Can this support a sponsored data benefit?
Yes, when the supported charging and traffic-policy setup matches the offer. Define precisely which traffic is covered and what happens outside the allowance or allowlist.
