Why are programs/actions being blocked?
Security Policies are used to harden our Cyber Security Posture to prevent intended and unintended malicious programs, applications, or actions. Our environment is unique as we have business, academic, and student functions which means we need an equally unique security controls. Security controls are based on least privilege, so access starts from being block/prevented and access is granted as needed.
Exception Process
This service provides a way for users to submit a request to review the event and create an exception if warranted. The security team will review and discuss the exception with the requester.
Approved exceptions:
- Approved by Security Policy Reviewers.
- Security Risk is accepted and controls are created.
- Controls will be tested, prior to release.
- Scope of control will be applied based on the review and details provided.
- Follow up with user to ensure controls are working.
Denied Exceptions:
- Technician or designees will reach out to user to discuss why request was denied.
- Direct to alternative products or approved actions (exception not needed).
Policy Reviewers
Technology Services Security Team
Expectations
Policies take time to apply and test. There is no guarantee that the exception can be applied in a short fashion. This also depends on the complexity of the security control.
To help the expedite the process:
- Details: Provide as much details as possible to reduce discovery/investigation time
- Lead Time: Test application prior to use. Submit ticket sooner rather than later.