Evasion

-

Evasion techniques are used by attackers to bypass security controls and avoid detection by security systems during a cyber attack. Evasion techniques are designed to exploit vulnerabilities in security systems or take advantage of weaknesses in the system's configuration to hide the attacker's actions.

Some common evasion techniques include:

  1. Fragmentation: Fragmentation is a technique where attackers break up their attack into smaller pieces to evade detection by intrusion detection and prevention systems (IDPS). Fragmentation works by splitting the attack into smaller packets that are sent over the network separately, so they may not be detected by IDPS.

  2. Encryption: Encryption is a technique where attackers encrypt their malicious traffic to avoid detection by network monitoring tools. This technique makes it difficult for security systems to detect the presence of the attacker's traffic on the network.

  3. Obfuscation: Obfuscation is a technique where attackers modify the code of their malware to make it difficult for antivirus software to detect. This can include adding junk code or using encryption to hide the actual code of the malware.

  4. Traffic Manipulation: Traffic manipulation involves modifying the network traffic of an attack to make it appear as legitimate traffic. This can include modifying the source IP address, port numbers, and other network protocols to avoid detection.

  5. Timing: Attackers may use timing techniques to avoid detection by security systems. For example, they may delay their attack until a specific time when the network is less active or when security systems are less likely to detect their activity.

Overall, evasion techniques are designed to make it difficult for security systems to detect and prevent attacks. To effectively defend against these techniques, security professionals must continuously monitor and analyze network traffic, update security systems to detect new threats, and use a combination of preventive and detective controls to protect against cyber attacks

Comments

Post a Comment

Popular posts from this blog

OpenSolaris and Linux virtual memory and address space structures

-
OpenSolaris and Linux virtual memory and address space structures Read Aloud Stop Reading OpenSolaris and Linux virtual memory and address space structures OpenSolaris and Linux are both popular operating systems that use virtual memory to manage system resources. In this article, we will compare the virtual memory and address space structures of OpenSolaris and Linux. Segmented address space model OpenSolaris uses a segmented address space model, where the address space is divided into multiple segments, each of which is used to store a specific type of data. For example, the text segment is used to store executable code, while the data segment is used to store global and static variables. This model allows for more efficient memory allocation and management, as it reduces the fragmentation of memory. Linux, on the other hand, uses a flat address space model, where the entire address space is treated as a single unit. This model is simpler than the segmented mode
Click Here to Read

Tying top-down and bottom-up object and memory page lookups with the actual x86 page translation and segmentation

-
Tying top-down and bottom-up object and memory page lookups with the actual x86 page translation and segmentation Read Aloud Stop Reading Tying top-down and bottom-up object and memory page lookups with the actual x86 page translation and segmentation Object-oriented programming (OOP) and virtual memory management are two essential concepts in modern computer systems. In this article, we will explore the connection between the top-down and bottom-up approaches used in OOP and memory page lookups, and the x86 page translation and segmentation mechanisms. Top-Down and Bottom-Up Approaches in OOP In OOP, two main approaches are used to design and implement software systems: top-down and bottom-up. The top-down approach starts with the system's high-level requirements and design, and then the details are gradually added until the system is fully specified. The bottom-up approach, on the other hand, starts with the low-level details and gradually bui
Click Here to Read

OpenSolaris and UNIX System V system administration pragmatics: service startup, dependencies, management, system updates

-
Read Aloud Stop Reading System administration is an important aspect of managing any operating system, and OpenSolaris is no exception. In this article, we will discuss some of the pragmatic approaches to system administration in OpenSolaris, including service startup, dependencies, management, and system updates. Service Startup: One of the primary tasks of system administration is to manage the startup of various services on the system. In OpenSolaris, this is done using the Service Management Facility (SMF). SMF provides a uniform and consistent way to manage services across the system. SMF is based on the concept of service instances, where each service is defined as an instance of a service contract. Service contracts define the characteristics of the service, including its dependencies, runtime properties, and logging information. SMF provides a number of commands that allow administrators to manage services. The svcs command lists the current status of all servic
Click Here to Read