Abstract: Examples of the present disclosure describe systems and methods for restricting access to application programming interfaces (APIs). For example, when a process calls an API, the API call may be intercepted by a security system for evaluation of its trustfulness before the API is allowed to run. Upon intercepting an API call, the process calling the API may be evaluated to determine if the process is known to the security system, such that known processes that are untrusted may be blocked from calling the API. Further, when the security system cannot identify the process calling the API, the security service may evaluate a call stack associated with the call operation to determine if attributes of the call operation are known to the security system. If the call operation is known to the security system as untrusted, the call operation may be blocked from calling the API.

Abstract: The present disclosure relates to systems and methods for identifying highly sensitive modules and taking a remediation or preventative action if such modules are accessed by malicious software. For example, the likelihood that a module is used for an exploit, and is thus sensitive, is categorized as high, medium, or low. The likelihood that a module can be used for an exploit can dictate whether, and to what degree, an application accessing the module is “suspicious.” However, in some instances, a sensitive module may have legitimate reasons to load when used in certain non-malicious ways. The system may also consider a trust level when determining what actions to take, such that an application and/or user having a higher trust level may be less suspicious when accessing a sensitive module as compared to an application or user having a lower trust level.

Abstract: Examples of the present disclosure describe systems and methods for malicious software detection based on API trust. In an example, a set of software instructions executed by a computing device may call an API. A hook may be generated on the API, such that a threat processor may receive an indication when the API is called. Accordingly, the threat processor may generate a trust metric based on the execution of the set of software instructions, which may be used to determine whether the set of software instructions poses a potential threat. For example, one or more call stack frames may be evaluated to determine whether a return address is preceded by a call instruction, whether the return address is associated with a set of software instructions or memory associated with a set of software instructions, and/or whether the set of software instructions satisfies a variety of security criteria.

Abstract: Examples of the present disclosure describe systems and methods for restricting access to application programming interfaces (APIs). For example, when a process calls an API, the API call may be intercepted by a security system for evaluation of its trustfulness before the API is allowed to run. Upon intercepting an API call, the process calling the API may be evaluated to determine if the process is known to the security system, such that known processes that are untrusted may be blocked from calling the API. Further, when the security system cannot identify the process calling the API, the security service may evaluate a call stack associated with the call operation to determine if attributes of the call operation are known to the security system. If the call operation is known to the security system as untrusted, the call operation may be blocked from calling the API.

Abstract: A core collector for collecting aeration cores lifted from a ground surface by a ground aerator machine includes a skid plate having a bottom surface opposite the ground surface and a top surface opposite the bottom surface. The skid plate has a plurality of openings in the skid plate extending between the top surface and the bottom surface at a proximal end of the skid plate. The plurality of openings are spaced apart from each other based on a spacing of extraction tines of the ground aerator machine. The core collector has at least one core clearing member. Aeration cores are deposited directly onto the top surface of the skid plate. The at least one core clearing member is configured to clear the aeration cores from the proximal end of the skid plate toward the distal end of the skid plate.

Abstract: A core collector for collecting aeration cores lifted from a ground surface by a ground aerator machine includes a skid plate having a bottom surface opposite the ground surface and a top surface opposite the bottom surface. The skid plate has a plurality of openings in the skid plate extending between the top surface and the bottom surface at a proximal end of the skid plate. The plurality of openings are spaced apart from each other based on a spacing of extraction tines of the ground aerator machine. The core collector has at least one core clearing member. Aeration cores are deposited directly onto the top surface of the skid plate. The at least one core clearing member is configured to clear the aeration cores from the proximal end of the skid plate toward the distal end of the skid plate.

Abstract: A golf handicap smart card system including at least one golf handicap smart card, at least one golf handicap smart card reader, and a golf handicap web site accessible by qualified users, wherein a qualified user has a current verifiable golf handicap with them at all times and available for peer review.

Abstract: A golf handicap smart card system including at least one golf handicap smart card, at least one golf handicap smart card reader, and a golf handicap web site accessible by qualified users, wherein a qualified user has a current verifiable golf handicap with them at all times and available for peer review.

Abstract: A data communications system which includes a plurality of terminals TL.sub.1 -TL.sub.5) and a data bus (DB), wherein each of the terminals has autonomous access to the data bus. Each terminal includes a receiver (114) which is normally enabled to receive messages on the data bus and which provides a signal (ADA) signifying the absence of messages. A transmitter (120) within each terminal includes a protocol control unit (140) which enables the transmitter to initiate message transmission only upon (i) the detection of an absence of messages on the data bus whose duration substantially equals that of a sync gap that is common to all of the terminals, and (ii) the subsequent detection of an absence of messages on the data bus whose duration substantially equals that of a terminal gap that is unique to the terminal, with the duration of the sync gap being greater than the duration of any terminal gap.