Every day, after you get your first cup of coffee, do you scan the mainframe security system violation and logging reports looking for abnormal behavior, strange activity, etc.? Given the size of.
This segment of my series was authored by Peter Hager and Earl Rasmussen of Net’Q (www.net-q.com). I thank them for their input since the network connected to our mainframes must also be secured.
Now that you have eliminated all the z/OS system integrity vulnerabilities you could find, re-evaluated your user validation to minimize the possibility of credentials being stolen, found all your.
Information and innovation are the most valuable commodities in our increasingly digital world. Thanks to the IT revolution, we now enjoy virtually instant categorization and access to key enterprise.
That’s the thing about myths: they’re only partly true.
Yes, File Integrity Monitoring (FIM) has been part of the distributed computing landscape for a few years now. And yes, real-time enterprise.
Now that we’ve gone through verifying that your system has no known integrity vulnerabilities, users are validated in a manner that will minimize the chance of someone stealing their identity and.
Not so fast…what about MFIM.
File Integrity Monitoring (FIM) has been part of the distributed landscape for years, generally as a component of an enterprise anti-malware strategy. But as attacks.
Mainframe Security: Part 3 - Where is all your sensitive data?
One vulnerability I see a lot are copies of sensitive data outside of the production environment. This sensitive data, if disclosed, can.
Mainframe Security Part 2: User Authentication
How can a system accurately determine whether access to data should be allowed when it is not certain who the user is? We have seen this in the NSA -.
Mainframe Security Part 1: System Integrity
I’m often asked about what installations can do to maximize their data security in an IBM mainframe environment. For those that do not know me, I was.