2017 April Highlights

Starling Platform:

Collaboration Features: Following up from last release there are now two ways to access Starling applications:  With a “personal” account or with a “work” account.  The work account is tied back to your company’s Azure Active Directory, which makes for an ideal sign-up and sign-in experience.  However, you really don’t need to know any of this to access a Starling application.  Just click sign-in and enter your work email and the rest is handled automatically, if your account is tied to Azure AD.

If you are using your work account to access a Starling app, we’ve made team collaboration easier too.  Once inside your Starling app, such as Starling Two-Factor Authentication, you can visit the Collaborator’s screen.  To invite someone from inside your organization to collaborate, you can search your Azure Active Directory to invite the team member.  You can still collaborate with someone outside your Azure AD but you’ll need to enter their email so they receive the invite.

Identity Analytics:

Our upcoming Identity Analytics and Risk Intelligence (IARI) solution is progressing nicely.  What’s new for this roll-out? We continue to add several features-in-motion that we’ll touch on here.

Dashboard View: The initial page and first widgets are out.  More are planned but this lets us roll out some of the underlying visual controls. One of the widgets provides interactive controls by clicking on the label at the bottom.  We’ll be reviewing your feedback to track which metrics will add the most value for the Dashboard.

Notification Update: We’ve added another level of detail to the audit information, and we’ve added new filters to the notification center.  You can see these changes in your preview environment by making changes to your collector settings, or by making changes to your data source and initiating a manual entitlement collection. 

Starting on Permissions:   This one will be a work-in-progress for several more sprints.  Currently we’ve surfaced granular permission information in three areas:  On the Rules page, on the High Risk Accounts page, and on the Compare Entitlements page.  It’s clear in our early prototyping that there is a need to provide this level of detail but that we need to drive it with a simple interface.  If you consider the Rules page, this is where you determine how you want to filter the underlying entitlement data and assign risk.  It is important to understand exactly what the rule is matching when it determines the risk so permission-level views are provided. But what we don’t want to lose is how best to translate the details into a simple-to-grasp concept. For example “Any account that can reset another user’s account in Active Roles is high risk”.  We’ll be making lots of changes here over the next several sprints as we tune the underlying details with a need for a simple-to-use interface.

Anonymous