Default Account Access
This report provides a six-month rolling view of attempts to access cardholder systems using default user accounts. This report looks at all activity by accounts categorized in the identity table with
tag=default. A default list of accounts is provided in the identity table, which can be edited from the Content Management page.
Relevant data sources
Relevant data sources for this report includes Windows Security, Unix SSH, and any other application, system, or device that produces authentication data. The report looks at data in the the Authentication data model.
How to configure this report
- Index authentication data from a device, application, or system in Splunk platform.
- Map the data to the following Common Information Model fields.
host, action, app, src, src_user, dest, user. CIM-compliant add-ons for these data sources perform this step for you.
- Set the category column of the Identity table to
defaultfor all accounts that are considered default accounts.
The data in the Default Account Access report is populated by the Authentication data model.
Useful searches for troubleshooting
|Verify that you have data from your network devices.
|Returns data from your network devices.
|Verify that authentication data is indexed in Splunk platform.
|Returns all default account activity data from your devices.
|Verify that default user accounts are tagged properly.
|Returns all a list of all default account activity.
|Verify that authentication attempts for default users are returned.
|Returns a list of all default account authentication activity.
|Verify that authentication data is normalized to the Common Information Model properly.
|`authentication` | fields sourcetype, action, app, src, src_user, dest, user
|Returns a list of events and the specific default account activity fields of data populated from your devices.
The report displays all attempts from users in either the
The assets table includes user information for default accounts such as root, network service, and other accounts that can produce a lot of data. Customers might not want to include that data in the report. They can modify the assets table to exclude particular users.
Network Traffic Activity
Insecure Authentication Attempts
This documentation applies to the following versions of Splunk® App for PCI Compliance: 5.0.1, 5.0.2, 5.1.0, 5.1.1, 5.1.2, 5.2.0, 5.3.0