antimalware_software
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
antimalware_software [2025/08/28 15:00] – ultracomfy | antimalware_software [2025/08/30 16:26] (current) – ultracomfy | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Information Technology/ | + | <WRAP column right 18%> |
+ | {{page> | ||
+ | </ | ||
+ | ~~Title: | ||
+ | <WRAP centeralign> | ||
+ | <fs xx-large> | ||
- | An antimalware program is a type of software used in the detection of and defense against malicious programs and exploits. Electronic devices can store all kinds of data, most importantly login credentials, | + | An antimalware program is a type of software used in the detection of and defense against malicious programs and exploits. |
+ | |||
+ | Electronic devices can store all kinds of data, most importantly login credentials, | ||
Most commonly, this is done through software, which is then called " | Most commonly, this is done through software, which is then called " | ||
- | ############################## | + | ====== |
- | ################### | + | ===== 0. Basics |
In general, the objective of an antivirus is to (1) prevent malicious code from ever executing on your system in the first place or, failing that, to (2) terminate a process if it is deemed to be malicious. | In general, the objective of an antivirus is to (1) prevent malicious code from ever executing on your system in the first place or, failing that, to (2) terminate a process if it is deemed to be malicious. | ||
- | ################### | + | ===== 1. Signature Detection |
- | Files are identifiable. With fancy mathematics, | + | Files are identifiable. With fancy mathematics, |
From here on, your life is simple. If someone gets infected, they call you and say "hey, we got infected by something, we don't know what", you find the source of the infection, you determine the signature of the file, add it to your list and with the next hourly " | From here on, your life is simple. If someone gets infected, they call you and say "hey, we got infected by something, we don't know what", you find the source of the infection, you determine the signature of the file, add it to your list and with the next hourly " | ||
Line 25: | Line 32: | ||
Critics will harp on and on about " | Critics will harp on and on about " | ||
- | ################### | + | ===== 2. Static Analysis |
Back to the start. We are an antivirus product. We are trying to protect the user from malicious code. The user is attempting to open a program. We stopped that attempt for now, because before we let a program execute we want to make sure that it is safe. So, the first thing we did was to run the program against our signatures. That test comes back negative. Well, cool, this means that we haven' | Back to the start. We are an antivirus product. We are trying to protect the user from malicious code. The user is attempting to open a program. We stopped that attempt for now, because before we let a program execute we want to make sure that it is safe. So, the first thing we did was to run the program against our signatures. That test comes back negative. Well, cool, this means that we haven' | ||
Line 35: | Line 42: | ||
The advantage to this approach is that it can get a pretty good insight into what a program may do without loading it into memory yet. This is critical because conventional malware can remain dormant on disk without causing harm; it is when it is loaded into memory (be it through the user executing it, or because of a scheduled task or through an autorun entry) that it starts doing malicious things. Analysing software without loading it into memory lets us look at the program without worrying too much. | The advantage to this approach is that it can get a pretty good insight into what a program may do without loading it into memory yet. This is critical because conventional malware can remain dormant on disk without causing harm; it is when it is loaded into memory (be it through the user executing it, or because of a scheduled task or through an autorun entry) that it starts doing malicious things. Analysing software without loading it into memory lets us look at the program without worrying too much. | ||
- | ################### | + | ===== 3. Sandboxing |
In cybersecurity terms, a sandbox refers to a protected virtual environment segmented off from the rest of the system, filled with all the sand imaginable but, ultimately, constrained to the sandbox. The box part here is the important part, as it means that nothing from inside that box can get out. Critically, this means a sandboxed program cannot access your data. This makes it perfect as a testing ground - throw a software sample in there and let it do its thing. Observe its behavior. Does it do anything scary? | In cybersecurity terms, a sandbox refers to a protected virtual environment segmented off from the rest of the system, filled with all the sand imaginable but, ultimately, constrained to the sandbox. The box part here is the important part, as it means that nothing from inside that box can get out. Critically, this means a sandboxed program cannot access your data. This makes it perfect as a testing ground - throw a software sample in there and let it do its thing. Observe its behavior. Does it do anything scary? | ||
Line 47: | Line 54: | ||
The cool thing about sandboxing, though, is that it too is able to independently identify malware, even if sample wasn't previously known. | The cool thing about sandboxing, though, is that it too is able to independently identify malware, even if sample wasn't previously known. | ||
- | ################### | + | ===== 4. Behavioral Detection |
Behavioral detection is what truly distinguishes good products from terrible ones. It is, however, also the hardest to get right, if you get it working at all. Of course we as humans don't care about cybersecurity in terms of software or code. As a company, you don't want internal documents to be exfiltrated to a hacker group - what you want is a system that can stop //that//, not just " | Behavioral detection is what truly distinguishes good products from terrible ones. It is, however, also the hardest to get right, if you get it working at all. Of course we as humans don't care about cybersecurity in terms of software or code. As a company, you don't want internal documents to be exfiltrated to a hacker group - what you want is a system that can stop //that//, not just " | ||
Line 58: | Line 65: | ||
The downside is that behavioral detection is //hard//. To understand which system operations exactly are // | The downside is that behavioral detection is //hard//. To understand which system operations exactly are // | ||
- | ############################## | + | ====== |
- | ################### | + | ===== 1. Common Sense ===== |
Common sense is the single most frequent advice that can be found on the internet. And it's true - human judgement can be a good and sometimes even the most effective layer of protection against threats of all kind. But.. who doesn' | Common sense is the single most frequent advice that can be found on the internet. And it's true - human judgement can be a good and sometimes even the most effective layer of protection against threats of all kind. But.. who doesn' | ||
Line 68: | Line 75: | ||
Risk management, a proper science that would //never// even //think// about suggesting something as ridiculous as this, is about minimizing risks at every stage of the process - at the human level, sure, but also at the mechanical level. That's why 50% of the resources of product design go into researching how humans could possibly fuck up using the product, and then minimizing the ways in which it can happen in the first place or how to minimize the potential damage. | Risk management, a proper science that would //never// even //think// about suggesting something as ridiculous as this, is about minimizing risks at every stage of the process - at the human level, sure, but also at the mechanical level. That's why 50% of the resources of product design go into researching how humans could possibly fuck up using the product, and then minimizing the ways in which it can happen in the first place or how to minimize the potential damage. | ||
- | And I haven't even talked about the things that are //outside// of your control. Supply chain attacks | + | And that still doesn’t cover risks beyond |
- | + | ||
- | + | ||
- | ################### | + | |
- | There is a pervasive myth that common sense plus Windows Defender are enough to keep you safe. Or that Windows Defender is as safe or safer than other products on the market. Now obviously, " | + | |
- | + | ||
- | And... I don't know, maybe? Funnily enough, despite arguing against it, that particular combination //is// what I rely on((And even that only because I can't disable Defender without some drama from the operating system.)). How much risk is acceptable risk for you? Either way, the reason I don't like that claim is because Common Sense is terrible advice on its own and, for the longest time, Windows Defender was terrible advice as well. | + | |
- | The truth is that the people who say " | + | ===== 2. What not to rely on: Windows Defender? ===== |
+ | There is a pervasive myth that common sense plus Windows | ||
- | For the longest time, Defender was a // | + | Maybe. In fact, that’s |
- | In those old tests, Windows | + | For years, Defender |
- | One annoying part about this now is that Defender has actually been catching up over the years. It now passes | + | Now, Defender has improved. It finally catches |
- | The reality is that Defender, despite having caught up as a cheap antimalware product that has a register of signatures, doesn' | + | Even so, Defender |
antimalware_software.1756386048.txt.gz · Last modified: 2025/08/28 15:00 by ultracomfy