Release Notes

 


New security controls

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.

New security controls

Role-based personalization

Role-based personalization can extend the administrative user experience and the application visibility controls in the user interface. The customer benefits are many. A few examples include:

SSL compression

The Splunk data transited across the network through Splunk forwarders is now compressed. Standard compression rates vary by type of data, but common compression numbers for static data types suggest that over 70% data compression is a strong possibility. Your mileage may vary.

SSLv3 support

The SSL v3 capability can be set as a default behavior in the Splunk environment.

Added cipher suite support

The added security controls include ciphers suites support. These ciphers include asymmetric key algorithms for signing and verifying; the RSA and DSA algorithms. The symmetric key algorithms for encrypt and decrypt operations include 3DES and AES in several modes with user selectable key lengths. For hashing, Splunk supports the approved SHA-1 algorithm. For message integrity Splunk supports HMAC-SHA-1 with varied HMAC blocksizes sizes in support up to 512.

Benefits

Any security conscious customer can be assured Splunk meets strict security guidelines for protocols and ciphers suites. In addition, Splunk extends the security controls to allow for enhanced network throughput via SSL compression and extends the access control model to allow for role based personalization of Splunk UI objects.

This documentation applies to the following versions of Splunk: 4.0 , 4.0.1 , 4.0.2 , 4.0.3 , 4.0.4 , 4.0.5 , 4.0.6 , 4.0.7 , 4.0.8 , 4.0.9 , 4.0.10 , 4.0.11 View the Article History for its revisions.


You must be logged into splunk.com in order to post comments. Log in now.

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.