Abstract: Different instances of a policy management system, in different clusters of a computing environment, can be configured differently for different purposes. Different policy databases, associated with the different instances of the policy management system, can store different sets of policy data that may be used or accessed during software testing or other operations via the different instances of the policy management system. A resolver can use a lookup table to track which instances of the policy management system are associated with corresponding instances of policy data. External services that access policy data during software tests and/or other operations can query the resolver to determine which instances of the policy management system to communicate with to access particular instances of policy data, such that the services can interact with differently-configured instances of the policy management system without the services themselves being reconfigured or changed.

Abstract: A protector server located in the Web traffic between an end-user computer and a Web site intercepts requests for Web pages from the Web site. The server inserts protection code into a Web page returned to the user computer which executes within the user browser. The code disables malware executing within the user browser by establishing itself as an event handler, finding likely malware in the stack, and disabling it. The code thwarts host-based malware by establishing itself as an event handler, and encrypting data fields of forms before the form is submitting to the operating system of the user computer. The code detects a Web inject attack by calculating a fingerprint for a form on the Web page and sending that fingerprint to the server. The server compares that fingerprint with one previously calculated for the form and generates an alert if different. The code detects a phishing attack by sending a notification to the server indicating within which domain it is executing.

Abstract: A protector server located in the Web traffic between an end-user computer and a Web site intercepts requests for Web pages from the Web site. The server inserts protection code into a Web page returned to the user computer which executes within the user browser. The code disables malware executing within the user browser by establishing itself as an event handler, finding likely malware in the stack, and disabling it. The code thwarts host-based malware by establishing itself as an event handler, and encrypting data fields of forms before the form is submitting to the operating system of the user computer. The code detects a Web inject attack by calculating a fingerprint for a form on the Web page and sending that fingerprint to the server. The server compares that fingerprint with one previously calculated for the form and generates an alert if different. The code detects a phishing attack by sending a notification to the server indicating within which domain it is executing.

Abstract: A protector server located in the Web traffic between an end-user computer and a Web site intercepts requests for Web pages from the Web site. The server inserts protection code into a Web page returned to the user computer which executes within the user browser. The code disables malware executing within the user browser by establishing itself as an event handler, finding likely malware in the stack, and disabling it. The code thwarts host-based malware by establishing itself as an event handler, and encrypting data fields of forms before the form is submitting to the operating system of the user computer. The code detects a Web inject attack by calculating a fingerprint for a form on the Web page and sending that fingerprint to the server. The server compares that fingerprint with one previously calculated for the form and generates an alert if different. The code detects a phishing attack by sending a notification to the server indicating within which domain it is executing.

Abstract: Disclosed is a system and method for detecting and mitigating the writing of sensitive or prohibited information to memory or communication media. The method includes detecting if an application is to write data to a memory, rerouting the writing of that data, and scanning the data for sensitive content or prohibited information. The scanning is done in accordance with one or more information security policies. If sensitive information is detected, the system has the option of issuing an alarm and/or preventing the sensitive information from being written, depending on the security policy. If the system permits the sensitive information to be written to memory, the system may spawn a file watcher object, which waits for a specified amount of time and then checks to see if the sensitive information has been deleted. If not, the system may issue an alarm or erase the sensitive information, depending on the security policy.

Abstract: A ridge vent for covering an open ridge of a roof comprises an elongated panel with two opposed lateral edges; a pair of elongated sidewalls extending downward from one of the lateral edges; a pair of elongated floor portions each extending outward from one of the sidewalls, each floor portion having an underside; and a sealant on the underside of at least a part of each floor portion to improve the seal between the floor portions and the roof.

Abstract: A ridge vent for covering an open ridge of a roof comprises an elongated panel having two opposed lateral edges; a pair of elongated sidewalls, each extending downward from one of the lateral edges; a pair of elongated floor portions, each extending outward from one of the sidewalls; a pair of elongated baffles, each extending upward from one of the floor portions, each baffle combining with one of the sidewalls and one of the floor portions to form an elongated trough along one side of the panel; and a filtering structure over each trough between the sidewall and the baffle to prevent particles and debris from collecting in the trough while allowing free flow of air.