Join our live webinar on June 18th to learn why Sequel Data Warehouse is the trusted tool for IBM i organizations to overcome the many types of data integration challenges.
The most overlooked aspects of IBM i compliance with PCI-DSS, SOX, HIPAA, and other standards, how to configure them correctly, and what Fortra can do to help.
This guide discusses the technical issues relevant to logging IBM i security data and offers a solution for real-time awareness of security events and integration with SIEM solutions.
SIEM (security information and event management) software provides insights into potential security threats through data normalization and threat prioritization, giving IT professionals an effective method of automating processes and centralizing security management in a way that helps them simplify the difficult task of protecting sensitive data.
While everyone likes to feel special, we need to be more selective when it comes to data access. As we discussed last month, many users have privileges far beyond their business requirements and simply need to have their access reduced to more reasonable levels.
Watch this in-depth feature tour to see how our SIEM solution, Powertech Event Manager, combats alert fatigue and translates data into actionable intelligence, allowing security teams to stay ahead of the curve.
Satisfy your auditor requirements with reports that provide a complete audit trail of privileged user activity with Powertech Authority Broker for IBM i. Schedule a demo today.
Despite the avalanche of regulations, news headlines remain chock full of stories about data breaches, all initiated by insiders or intruders masquerading as insiders.
During an audit a few years ago, I revealed to the client’s security team that corporate payroll information on every employee, including the CEO, was being archived in an output queue (called PAYROLL) for weeks at a time. Due to poor configuration, this information was accessible to every employee.
There are several considerations with authority adoption. Each is important but can usually be accommodated. But what is the effect if the program owner has the same or less privileges than the user that called the program?