Knowledgebase

Controlling Access to Applications Print

  • googletechnology, google, guide, howto, solution, zillionkinghost, hosting, support
  • 0

Identity-aware access.

WHAT IDENTITY-AWARE ACCESS PROVIDES

Authentication and authorisation enforced before a request reaches your application.

WHAT THAT REPLACES

A network perimeter, or authentication built into every application.

WHY THAT MATTERS

Internal tools can be reachable from anywhere without being exposed to everyone.

WHAT IT SUITS

Internal applications Administrative interfaces Anything that was previously protected only by being on a private network

WHAT TO CONFIGURE

Which identities and groups may reach each application Conditions, such as device state or location

WHAT IT REMOVES THE NEED FOR

A virtual private network, for web applications.

WHAT TO STILL DO

Authorise within the application, on the specific record.

WHY

The proxy establishes who someone is, not what they may see.

WHAT TO PASS THROUGH

Verified identity information, which the application can trust.

WHAT TO VERIFY

That the application cannot be reached directly, bypassing the proxy.

WHY

Otherwise the protection is optional.

WHAT TO AUDIT

Access grants, periodically.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot