Abstract: Techniques for verifying a signature of an executable file are disclosed. In one particular exemplary embodiment, the techniques may be realized as a computer-implemented method for verifying a signature of a first executable file, comprising creating a first functional flow graph from the first executable file, storing the first functional flow graph, receiving, using a processor, a rule for the first executable file, and storing the rule. The techniques may also comprise receiving a second executable file, creating a second functional flow graph from the second executable file, determining whether a difference between the first functional flow graph and the second functional flow graph is less than a tolerance, and when it is determined that the difference between the first functional flow graph and the second functional flow graph is less than the tolerance, applying the rule to the second executable file.

Abstract: Methods, apparati, and computer program products enforce computer network security policies by assigning network membership to a client (105) based on the client's compliance with the security policies. When a client (105) requests (305) a network address, the DHCP proxy (110) intercepts the request and assigns (350) that client (105) a logical address on the protected network (140) if the client (105) is in compliance with the security policies. If the client (105) is not in compliance with the security policies, in various embodiments, the DHCP proxy (110) assigns (350) the client (105) an address on a restricted network (145) or no network address at all.

Abstract: Methods, apparati, and computer program products enforce computer network security policies by assigning network membership to a client (105) based on the client's compliance with the security policies. When a client (105) requests (305) a network address, the DHCP proxy (110) intercepts the request and assigns (350) that client (105) a logical address on the protected network (140) if the client (105) is in compliance with the security policies. If the client (105) is not in compliance with the security policies, in various embodiments, the DHCP proxy (110) assigns (350) the client (105) an address on a restricted network (145) or no network address at all.