When we plan for Applications (Web or Mobile), we need to think about different strategies. These types of questions arise:
- How will the application be published?
Centrify provides the user portal, however, depending on your environment, you may have an intranet or content management platform that is used as a hub for applications.
- What is the policy to access these applications?
Apps can have different assurance requirements. Maybe certain portions of the HR app are for intranet-only access with step-up (or two-factor) authentication. Maybe your Netsuite-based ERP should only be available from inside of the United States.
- Who should be entitled to access each app?
Your security team may want to grant access based role or job function. Centrify User Suite uses AD or Cloud Directory principals for app visibility.
- What are the authentication capabilities of the app?
Modern (especially cloud-based apps) provide federation technologies (like SAML, etc) but legacy apps don't have those capabilities or aren't available in the current version. Also (and unfortunately) not all apps may be looking at the corporate directory (e.g. AD) as the identity repository (which can enable Kerberos or NTLM). CUS offers the flexibility of password-vaulting and replaying.
- How is the application provisioning model?
This topic impacts the bottom-line of the business because the timely deprovisioning of cloud apps can impact the billing depending on how the application provider is metering the usage of the application. In addition, some apps need to have entitlements provisioned as well for the purposes of role-based access.
- What is the strategy for on-premise apps?
Are these apps accessible via an existing VPN infrastructure (e.g. CheckPoint, Cisco, Microsoft's DirectAccess or others) or will you make use of the Centrify App Gateway (VPN-less access)?
These are high-level categories, there are advanced topics like timeouts, attribute-mapping, provisioning of certificates for federation trust, etc; but we will cover each scenario individually.
We will start by publishing these Web applications:
- On-premises SharePoint (as a shortcut)
- On-premises Apache or Java-based apps (leveraging NTLM, Kerberos & ADFS-less WS-Fed apps)
- Google Apps
Later we'll move on to Mobile apps on the Google Play and Apple App Store.