If I were to say “Fort Knox,” you would picture something like Scrooge McDuck's vault overflowing with gold, yet the term “mainframe” is unlikely to get a similar reaction. In fact, many believe.
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.
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 -.
Over the last few weeks I have written that mainframe people and enterprise security people use “Syslog” to mean two different things and that z/OS SYSLOG is not a good source for the kinds of.
We hear every day of different viruses and attacks almost as if they were coming off an assembly line. They come in all shapes, sizes and forms, and they are becoming more sophisticated and.
The key to enabling actionable intelligence in your SIEM strategy is to have recurrent neural network capability to help manage events. Take this example for instance: If I react to an event, is.