News for hackers. Stuff that matters.
Re:Detecting malicious behaviour using system calls by xjay on Thursday July 28, 2016 @11:34PM (#12184880)
Related thoughts specifically concerning ransomware (controlling write access):

Operating systems with a GUI typically have file associations bound to executables. One could use that knowledge to restrict write access (or even read access), or at least use this fact; "application with no file associations does file I/O." Excluding known system executables, etc.

So if applied more strictly, an application that wasn't associated with .JPG or .JPEG couldn't write to those files, or perhaps not even read from them.

As for restricting read access, my first thought goes to browsers that may not be associated with every file type you want to upload/attach, but that could be a dialog between you and the system as it happens (allow it once/now/session, for N days, forever, etc).

Re:Detecting malicious behaviour using system calls by 13of40 on Friday July 29, 2016 @01:33AM (#12185172)
That's tough to do if the application in question is a script engine or is merely script-enabled like Excel or Word.

One ad-hoc thing you could do to beat some of the ransomware out there is remove or break things like vssadmin.exe so the ransomware can't prevent you from reverting to a previous version of a file. I don't know if mac has something analogous to this, though.