Perimeter Security Policy
As the saying goes, a chain is only as strong as its weakest link. This applies more than ever to cybersecurity implementations designed to protect organizations from malicious attacks, intruders and vulnerabilities.
While security principles should apply throughout the organization, locking down the perimeter and ensuring only necessary connections get through is an especially critical goal. Whether traffic is going from outside to inside or vice versa, having a strong, comprehensive and reliable perimeter security policy is integral to securing organizational data and the employees who use it to do their jobs and conduct company business.
The purpose of this policy, written by Scott Matteson for TechRepublic Premium, is to provide guidelines for securing the organization’s network perimeter.
Featured text from the policy:
Network layouts.
All public-facing servers should be segregated in a designated DMZ subnet, with only required services permitted in both an internal and external direction. No other devices should occupy or have access to this subnet.
All in-bound Internet services must be processed by a proxy server or using stateful inspection methods for traffic handling.
Enhance your security procedures with our seven-page policy document. Previously priced at $49, this is now available for download at just $9. Alternatively, enjoy complimentary access with a Premium annual subscription. Click here to find out more.
TIME SAVED: Crafting this content required 14 hours of dedicated writing, editing and research. Benefit from our expertise and improve your handling of perimeter security.
Resource Details
* Sign up for a TechRepublic Premium subscription for $299.00/year, and download this content as well as any other content in our library. Cancel anytime. Details here.
* Sign up for a TechRepublic Premium subscription for $299.00/year, and download this content as well as any other content in our library. Cancel anytime. Details here.