This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hi,
I like to reopen this old RFE/Idea for a reconsideration since we now are up to new challenges with the 'Digital Operations Resilience Act'.
By using a hashed signature either for a log or for specific IMS logrecords, an unauthorized update of a record will make it impossible to use as input to a database or system recovery.
If a 'signed log data hash' option is activated in eg. RECON, IMS will automatically add a hash to selected (specific or all) logrecords, these vaules will also be verify during DB or system recovery.
To have an option to provide a hash for all or some of the logrecords during the SLDS archive utility will make it more secure, easier and faster implementation for IMS installations, compared to do this as a client unique solution.
Thanks,
Curt
One approach could be to only hash and sign certain groups of log records, x01, x03, x5901, x5903 and also different database records related to changes (eg. these used in recovery). This would speed up the sign process but still increase security since a change to any record of this kind would be noticed when calculating the checksum in case of recovery.