Resources

Blog

An IBM i Hacking Tale

Discover how penetration testing can be used on IBM i systems to find hidden vulnerabilities in your security. This post breaks down Core Impact's IBM i pen testing process from discovery to privilege escalation.
Blog

What Is SIEM?

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.
On-Demand Webinar

Powertech Event Manager Feature Tour

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.
Datasheet

Powertech Risk Assessor for IBM i

Powertech Risk Assessor for IBM i automates the process of gathering security information. Schedule a demo today.
Datasheet

Powertech Authority Broker for IBM i

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.
Blog

Your IFS Is Probably a Treasure Trove of Unsecured Data

Consider the type of information contained in the PDFs in your directories and spooled files in your output queues. Aside from taking up disk space and consuming time during a backup, what's the issue with leaving these reports on the system? The issue is the contents of those reports, along with who has access to them.
Guide

Essentials for Privileged Access Management

Learn how you can effectively and efficiently control privileged UNIX and Linux accounts from accessing data or executing any application by using centralized access management.
Blog

How “Smash and Grab” Compromises IBM i

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.