Join IBM i security expert Amy Williams on June 20th to learn how to make your audit journal data more easily accessible and how to set up your audit journal so that critical information doesn’t go unnoticed.
Why haven’t IT processes kept pace with business changes? Why are you still suffering from downtime as the result of human error? Read this article to see how legacy processing methods are still leading to downtime today—and what you can do to stop it.
Many ERP packages have built-in schedulers. However, these schedulers are typically not flexible or robust enough to meet the needs of even the smallest data center.
PCI DSS now includes requirements for strong encryption of cardholder data. Learn how key management is an essential element of preventing unauthorized data access.
As you consider taking your IBM i to the cloud, cybersecurity will no doubt top your list of concerns. And for good reason. It’s important to remember that the cloud is kind of a lie. Your sensitive data is simply being sent to someone else’s server, and that server has a physical location somewhere.
Just like on-prem cybersecurity, IBM i cloud security can be divided into two parts:
...
How many separate job schedulers are you juggling? Don’t let your important processing into a scheduling circus. Stick with a single, sophisticated solution.
Your shop runs more than 30 jobs each day. Your jobs must communicate across IBM i and another OS. You need to monitor them and generate reports for audits or SLAs. Do your existing job schedulers really meet your needs?
Looking for better ways to integrate your Windows, AIX/UNIX, and Linux environments with the Robot Schedule scheduling system? Robot Schedule Enterprise commands can enhance your integration experience.
Typically, there are two main issues with monitoring a system manually: having to go out deliberately (and repeatedly) and check to see if something has happened; and the fact that you are most likely looking for the proverbial needle in a haystack of logged events.
When it comes to security on IBM Power Servers running IBM i, a common challenge for many organizations is the number of users with too much power. These users can potentially circumvent application controls, override security restrictions for themselves and others, change critical server configuration settings, and even cover their tracks while they do it.
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.
Ask any security professional which area of IBM i security is most often ignored and chances are that the unanimous response is a chorus of “the Integrated File System.” Although it’s been around since V3R1, the Integrated File System, or IFS, remains a shrouded mystery that represents significant risk to many IBM i organizations.
Your organization has invested in a security information event manager, or SIEM, to receive and analyse security and event log information from a variety of servers. Now they want to also get this information from their IBM Power Systems server.
Let’s face it; system administration remains a largely thankless task. From scheduling jobs to balancing workloads to answering messages in QSYSOPR, administrators and operators work diligently behind the scenes to ensure that IBM i servers are available to run mission-critical applications.