Authentication Application Security Incidents
Alert Logic can detect and generate security incidents from log data collected from third-party authentication application resources. Alert Logic collects log data through API-based integration with these applications. Authentication security incidents enhances your security content by providing greater visibility into threats in your environment.
Security incidents are generated when suspicious events are detected that require attention to maintain your security posture, achieve regulatory compliance, or both. Alert Logic organizes the incidents by threat level and classification type on your Incidents page. To learn more about the Incidents page, see Incidents.
About security incidents
Alert Logic generates security incidents related specifically to administrative actions, user logins, and user behavior, which are classified as authentication:activity and admin:activity in the Incidents page in the Alert Logic console. Alert Logic can generate security incidents from the following authentication applications:
- Cisco Duo
- Azure/Office 365 AD
For information about how to configure one of these authentication applications, see Security log configuration.
Security incident examples
Alert Logic generates and classifies the following security incidents from authentication application log data if detected in the Incidents page:
|Brute force activity ||
When brute force activity is detected from an IP address. An incident is triggered at a threshold of 250 log events for a single user, and at a threshold of 60 log events for multiple users.
|MFA disabled||Disabled MFA of a user from the sign-in logs||authentication:activity|
|User granted admin privileges||
User granted administrator privileges to another user.
|User attempted to access admin application||
User attempted to access an admin application.
|Multiple countries, single day||
Logins detected from multiple countries in one day.
|Credential stuffing activity||
A type of brute force activity where an attacker obtains leaked credentials from an unrelated breach and attempts to gain access to other accounts through credential reuse.
You must configure log collection for the authentication application in the Application Registry page in the Alert Logic console for Alert Logic to collect log data and generate incidents. The Application Registry page is a catalog with all of the available applications from which Alert Logic can receive log data. You can add multiple log collection instances to each application.
Configure an authentication application log collection instance
The instructions below provide a basic workflow for configuring an application. However, application requirements vary and often require different information. See the guide specific to the application you want to configure:
- Configure Auth0 Log Collector
- Configure Cisco Duo Log Collector
- Configure Microsoft Office 365 Log Collector
- Configure Okta Log Collector
- Configure Salesforce Log Collector
To see the full list of log collection instructions available, see Log Collectors Configuration Guide.
To add a new application collection:
- In the Alert Logic console, click the menu icon ().
- Click Configure, and then click Application Registry.
- On the Application List tab, use the drop-down menu to select the application type you want to see.
- Click GET STARTED from the available application you want to configure.
- Depending on the application, the required fields and options will vary. The general configuration requirements are the following:
- Under Details, type a name for the application.
- Under Collection Method and Policy, specify a location from where to collect log data, and provide the required credentials associated with your application account.
- Click ADD.
- In the Application List tab, if you have configured your application correctly, the application tile will say Configured.