Resources

On-Demand Webinar

Encryption on IBM i Simplified

DB2 Field Procedures (FieldProcs) were introduced in V7R1 and have greatly simplified encryption, often without requiring any application changes. Now you can quickly encrypt sensitive data on the IBM i.
Datasheet

Powertech Encryption for IBM i

Powertech Encryption for IBM i protects sensitive data using strong encryption, tokenization, integrated key management and auditing. 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.
Datasheet

Powertech Encryption for IBM i Compliance Datasheet

Satisfy Stringent Requirements for Encryption and Key Management Powertech Encryption for IBM i will help your organization meet compliance mandates through its integrated key management solution, and strong IBM i field encryption and backup encryption features. Powertech Encryption for IBM i utilizes AES and TDES encryption algorithms, both of which follow standard (non-proprietary)...
Guide

Download "IBM i Encryption: How to Protect Your Database"

    Learn your options for encrypting IBM i data. Sensitive information needs to be kept secret. That’s an indisputable fact for modern organizations, where sensitive information can include customers’ personally identifiable information, customer lists, and intellectual property. Encryption is widely recognized as the most effective way to ensure private information...
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.
Article

The Modern Alternative to Authority Adoption

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?