Kisco Systems

Kisco U

Security Enhancements in IBM i 7.6 TR3 and IBM i 7.5 TR9

Home : Kisco U : Security Enhancements in IBM i 7.6 TR3 and IBM i 7.5 TR9

In these TRs, IBM has closed major compliance and security visibility gaps. Customers are strongly advised to upgrade and implement CVE reporting and password monitoring.

Read the full TR announcements from IBM here:

New CVE service and table function

The QSYS2.cve_info Service which provides a list of the CVEs (Common Vulnerabilities and Exposures) that affect IBM i was released in a previous TR but these TRs have expanded on this feature and provides even more functionality to help us remain current – something that’s absolutely critical in the age of AI.

Two new SQL table functions have been added – one, SYSTOOLS.cve_ptf lists the CVEs that pertain to a particular release (IBM i 7.4, 7.5 and 7.6 are the options) along with their remediating PTFs or group PTFs. You can run this function regularly (say weekly) to determine if new CVEs have been issued and put a plan in place to apply the appropriate fix.

The second table function – SYSTOOLS.cve_currency – takes it a step further and provides an indication of whether the remediating PTF or group has been applied to the system where it’s being run! Woo hoo!  Gone are the days of determining which CVEs pertain to IBM i and if they do, going to the effort of determining which PTF or PTF group remediates them and then determining whether they’ve been applied! This is a HUGE time savings for any IBM i system administrator who wants to keep their system up to date and/or is required to prove that it’s up to date.

A big shoutout goes to Scott Forstie for this functionality. Parsing the website where the CVE information is held, determining the remediating PTF(s) or PTF group and whether they were installed was not a trivial exercise. Once he got it working Scott worked with several of the Navigator for i Advisors (including Steve Riedmueller and me) to ensure the information provided was the right information and presented in the most useful manner. Thank you, Scott!

Updates to the PS and PW Audit Journal Entry Types and Audit Journal SQL Helper Functions

Columns were added to both the PS (Profile swap) and PW (Password) audit journal entries. The Password Specification column was added to the PS entry to indicate the authentication method used on the profile swap.

Additions to the PW entry were more interesting (in my opinion.) The PW entry received a major enhancement. In addition to adding more types of authentication failures,  the audit entry now logs successful authentication attempts along with the authentication interface used, for example, a password, profile handle, profile token or NetServer sign on. Logging successful authentication and not only failed attempts is an important addition because it will you help track activity – for example, during a forensic investigation. It can also alert you to inappropriate activity if you’re sending your IBM i audit journal information to your SIEM. For example, you could put a rule in place to alert you to sign on activity from an unknown or inappropriate IP address range.

Both the QSYS2.audit_journal_PS and QSYS2.audit_journal_PW helper functions have been updated to include these new fields.

Helper functions were added in IBM i 7.6 (only) for the DI (Directory server) and X0 (Network authentication) audit journal entry types.

Digital Certificate Manager (DCM) API Enhancements

The reason for this enhancement may not be obvious, but the cause is due to the standard Ballot SC081v3. The CA/Browser Forum adopted this standard to increase web security by (eventually) requiring the renewal of digital certificates every 47 days. This requires the industry to move to automated certificate lifecycle management. These APIs provide the foundation for developing automated certificate management tools on IBM i. 

Navigator for i Updates

The CVE functionality is available in Navigator for i under the Security category (Click on the padlock icon.) Enhancements have been made to the TLS configuration wizard. And the Web Admin GUI has been migrated to Navigator for i, making it much easier to configure web instances to use TLS than it was when using the old interface.

I hope you’ll check out these enhancements and start taking advantage of them. I, for one, am thankful for each new feature IBM provides that supports my assertion that IBM i is the most secure-able system available.

 


Contributed by:
Carol Woodbury
IBM i Security Advisor
Kisco Systems