Abstract: Leak detection apparatus has an installable detector comprising a plurality of spaced apart electrical electrodes. A controller operably interfaces the plurality of electrical electrodes. The controller is configured for detecting a leak by detecting current flow through water pooled between the electrodes. The detector is installable within wall and void spaces surrounding wet areas such as bathroom baths, showers, cabinetry, kitchen and bathroom basins and the like. As such, the detector is able to detect a leak when a waterproof membrane is compromised, or movement and/or poor workmanship allows water to flow therethrough. The detector may comprise a flexible body which may be elongate for installation in tight spaces and around corners and/or a mat for covering large areas such as under baths and which may be cut to size to fit.

Abstract: A framework for a security system is described. The framework may be used to track which security engines are available to enforce security policies. A security engine is a software resource that enforces security policies designed to help ensure that a vulnerability of an application or operating system cannot be exploited. The framework may be used to maintain a holistic view of a status of computing devices that a security system is configured to operate with. The framework may enforce security policies uniformly across components of a security system by providing an application program interface. The security system may broker security enforcement events and security policies. By providing these services, the framework presents a unified model for interactions between software components and the security system.

Abstract: Techniques for securing applications and operating systems are provided. In an embodiment, the system notifies a user that a security enforcement action is being taken even though the condition prompting the action is detected by a security engine that executes in kernel mode. The security engine enforces security policies that help to ensure that a vulnerability of an application or operating system cannot be exploited. In an embodiment, the security system may solicit input from a user relating to a security enforcement action even though the condition prompting the action is detected by a security engine that executes in kernel mode. Security policies may be defined as sets of rules, each having a condition and an action. The security system thus enables kernel mode components to provide notifications to a user or solicit input from the user.

Abstract: A programming interface includes a first group of functions related to communicating a new security policy to multiple security engines. Each of the multiple security engines is configured to replace an existing security policy with the new security policy. The programming interface also includes a second group of functions related to communicating an indication of each security engine's readiness to implement the new security policy.

Abstract: A computer based digital transcription system employs audio and video inputs of a court proceeding, and stores the digital signals in a memory in the form of distinct file segments of a predetermined time length during each recording session. The computer associates a date and time and a third identifier, such as location, with each distinct file segment. Playback of any desired segment may be effected during recording or at any time afterward; and playback does not interfere with the recording of realtime information.

Abstract: A framework for a security system is described. The framework may be used to track which security engines are available to enforce security policies. A security engine is a software resource that enforces security policies designed to help ensure that a vulnerability of an application or operating system cannot be exploited. The framework may be used to maintain a holistic view of a status of computing devices that a security system is configured to operate with. The framework may enforce security policies uniformly across components of a security system by providing an application program interface. The security system may broker security enforcement events and security policies. By providing these services, the framework presents a unified model for interactions between software components and the security system.

Abstract: Languages for expressing security policies are provided. The languages comprise rules that specify conditions and actions. The rules may be enforced by a security engine when a security enforcement event occurs. The languages support data separation, dynamic evaluation, and ordered rule scope. By separating data from logic, security engines may only need to be updated with a portion of rules that change. With dynamic evaluation, expressions of rules may be evaluated dynamically, such as by querying a database, when a security engine enforces a rule. With ordered rule scope, when a security enforcement event implicates a number of rules simultaneously, the rules may be enforced in a deterministic and logically organized manner.

Abstract: Techniques for securing applications and operating systems are provided. In an embodiment, the system notifies a user that a security enforcement action is being taken even though the condition prompting the action is detected by a security engine that executes in kernel mode. The security engine enforces security policies that help to ensure that a vulnerability of an application or operating system cannot be exploited. In an embodiment, the security system may solicit input from a user relating to a security enforcement action even though the condition prompting the action is detected by a security engine that executes in kernel mode. Security policies may be defined as sets of rules, each having a condition and an action. The security system thus enables kernel mode components to provide notifications to a user or solicit input from the user.

Abstract: A programming interface includes a first group of functions related to communicating a new security policy to multiple security engines. Each of the multiple security engines is configured to replace an existing security policy with the new security policy. The programming interface also includes a second group of functions related to communicating an indication of each security engine's readiness to implement the new security policy.

Abstract: An illuminated cup holder assembly (10,10′) generally includes an elongated waveguide (12,12′), a cup holder bottom portion (14,14′), and a cup holder top portion (16,16′). The cup holder bottom portion (14,14′) includes a waveguide support (22,22′) disposed above a base (18,18′), with at least a portion of the waveguide (12,12′) disposed on the waveguide support. The cup holder top portion (16,16′) includes a shield (24,24′) extending over the waveguide (12,12′). This assembly (10,10′) splits the cup holder in two wherein the two pieces (14,14′ and 16,16′) create a pocket to hold the waveguide (12,12′) in place. In other words, the top and bottom portions (14,14′ and 16,16′) sandwich the waveguide (12,12′) into place.