This process describes how the College of Computing will adhere to USG and GT data center access policies and standards to physically protect data and assets in the data centers.
This process is to describe how the College of Computing will adhere to USG and OIT Security Incident policies and standards. It is not intended to replace any policies or processes from USG and OIT. Any conflicts with these policies or any other should be reported to the College of Computing Information Security Engineer Lead or TSO management
This primer aims to familiarize users with the myriad security challenges in today's computing landscape. While it can't cover every aspect, it serves to increase awareness of risks, promote a questioning attitude, and encourage the reporting of suspicious activity.
This process is to describe how the College of Computing will adhere to USG and OIT Vulnerability management policies and standards. It is not intended to replace any policies or processes from USG and OIT. Any conflicts with these policies or any other should be reported to the College of Computing Information Security Engineer Lead or TSO management.
The Purpose of this Hot-To is to explain when and how to use the Incident log. The more accurate the log, the more it is possible to recognize and record trends for reporting and possible proactive prevention measures.
Directions for annual cleanup and review of IPAM for housekeeping and security purposes. This procedure should precede firewall review and clean-up as it directly affects maintaining effective and secure firewall practices.
This process is to describe how the College of Computing will adhere to USG and OIT Security SSP and TCP by TSO involvement and tracking of equipment requiring TCPs and/or SSPs.