It provides currency support for z/OS 2.3 and RACF:
* policies for pervasive encryption of data with key labels
* connection protection with z Encryption Readiness Technology (zERT)
* extended reporting for Integrated Cryptographic Services Facility
* extended multi-factor authentication (MFA) options
It extends security intelligence and analytics capabilities:
* a zSecure Alert feed to HPE Security ArcSight
* a zSecure Admin Access Monitor feed to IBM Operations Analytics for z Systems
It provides currency support for:
* Db2 12
* Security Technical Implementation Guide (STIG) 6.31
Details can be found on the Service Management Connect - System z blog
in this blog entry by Jeroen Tiggelman.
This provides service for new DB2 region security settings, new SMF log event records, and a new DB2 object privilege.
You can find technical details on the Service Management Connect - System z blog, in this entry.
zSecure 2.1.1 has been announced on July 15, 2014, with a planned availability date of September 5, 2014.
This announcement includes a new product IBM
More details about the various integrations between zSecure and QRadar SIEM can be found in this blog entry by Jeroen Tiggelman on the Service Management Connect - System z blog.
You might also be interested in what else is new
On the System z Management blog, Jeroen Tiggleman has published a summ
zSecure is an excellent platform to help you secure your System z platform and can be used to detect both external and insider threats to your system. To find out more about how you can help detect insider threats in your IT environment, you can download and read "Sta
Mihal Iacob and Walid Rhaibi have just published "Res
From the article summary:
System administrators are responsible for, among other things, protecting a database against unauthorized access or misuse by authorized database users (for example, inappropriate access to sensitive information within a database). A common requirement to mitigate such risks is ensuring that users are allowed to connect to the database only from a list of trusted hosts or IP addresses that are known to be secure. This article gives a practical example of how such a requirement can be put in practice by making use of the CONNECT_PROC database configuration parameter of IBM® DB2® for Linux®, UNIX®, and Windows®.