Collaborate Disseminate
Recently, my nine-year-old son informed me that he had observed over time how I always seem to help other people and how others always depend on me. I said to him that, in a way, he is much the same, as he is always saying ‘yes’ to doing li… Continue reading Why ‘Yes Persons’ Make Change Control a Necessity for Your Company
If File Integrity Monitoring (FIM) were easy, everyone would be doing it. Actually, it is pretty easy. It’s not exactly rocket science. Practically anyone with a modicum of Python, Perl or development skills can write an app or a script to gather the c… Continue reading Superior Integrity Monitoring: Getting Beyond Checkbox FIM
File integrity monitoring (FIM) exists because change is prolific in organizations’ IT environments. Hardware assets change. Software programs change. Configuration states change. Some of these modifications are authorized insofar as they occur d… Continue reading What Is FIM (File Integrity Monitoring)?
When you work for the office of your organization’s chief information security officer (CISO), time is not your friend. In 2015, the average time from compromise to discovery of a security incident was 146 days. That figure dropped to 99 days in 2016. Even so, the pressure is still on for organizations to do more […]… Read More
The post ExpertOps: More Security with Less Time appeared first on The State of Security.
The post ExpertOps: More Security with Less Time appeared first on Security Boulevard.
I published the following diary on isc.sans.org: “Backup Scripts, the FIM of the Poor“. File Integrity Management or “FIM” is an interesting security control that can help to detect unusual changes in a file system. By example, on a server, they are directories that do not change often. Example with
[The post [SANS ISC] Backup Scripts, the FIM of the Poor has been first published on /dev/random]
Continue reading [SANS ISC] Backup Scripts, the FIM of the Poor