Monitoring Annotations
Annotations used for the dynamic monitoring of security policies.
Specurity Aspects
Name
Description
Maintain the correlation between security policies, aspects, and security properties
Specification Elements
Name
Description
Measures the execution time and monitors its exit status. Output: Start event, end event, duration, exit status, status information.
Captures changes made to attributes and logs the new value. Output: Attribute value on each assignment operation.
Combines method and attribute monitoring applied to all methods and attributes of the class. Output: Combines the method and attribute monitoring output.
Tracks the number of objects on the memory heap. Output: Global object counter.
Generates a signal whenever a function is called. Output: A “Ping” message is added to the log on each invocation.
Tracks the control flow of methods. Output: Same as method monitoring for each method encountered by the control flow.
Methods, attributes, and classes are excluded from the monitoring scope. Output: “Negative output”, curtails output of impacted code.
Security Aspects
Specification Elements
@Monitor
Measures the execution time and monitors its exit status. Output: Start event, end event, duration, exit status, status information.- Applies to:
- Activity
@Monitor
Captures changes made to attributes and logs the new value. Output: Attribute value on each assignment operation.- Applies to:
- Data
@Monitor
Combines method and attribute monitoring applied to all methods and attributes of the class. Output: Combines the method and attribute monitoring output.- Applies to:
- Entity
@Count
Tracks the number of objects on the memory heap. Output: Global object counter.- Applies to:
- Entity
@Ping
Generates a signal whenever a function is called. Output: A “Ping” message is added to the log on each invocation.- Applies to:
- Activity
@Taint
Tracks the control flow of methods. Output: Same as method monitoring for each method encountered by the control flow.- Applies to:
- Activity
@Exclude
Methods, attributes, and classes are excluded from the monitoring scope. Output: “Negative output”, curtails output of impacted code.