27.01.2014 Views

NIST 800-44 Version 2 Guidelines on Securing Public Web Servers

NIST 800-44 Version 2 Guidelines on Securing Public Web Servers

NIST 800-44 Version 2 Guidelines on Securing Public Web Servers

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

GUIDELINES ON SECURING PUBLIC WEB SERVERS<br />

Completed<br />

Acti<strong>on</strong><br />

Define a complete <strong>Web</strong> c<strong>on</strong>tent access matrix. Identify which folders and files within<br />

the <strong>Web</strong> server document should be restricted and which should be accessible (and<br />

by whom)<br />

Check the organizati<strong>on</strong>’s password policy and set account passwords appropriately<br />

(e.g., length, complexity)<br />

Use the robots.txt file, if appropriate<br />

C<strong>on</strong>figure anti-spambot protecti<strong>on</strong>, if appropriate (e.g., CAPTCHAs, nofollow, or<br />

keyword filtering)<br />

<strong>Securing</strong> <strong>Web</strong> C<strong>on</strong>tent<br />

Completed<br />

Acti<strong>on</strong><br />

Ensure that n<strong>on</strong>e of the following types of informati<strong>on</strong> are available <strong>on</strong> or<br />

through a public <strong>Web</strong> server<br />

Classified records<br />

Internal pers<strong>on</strong>nel rules and procedures<br />

Sensitive or proprietary informati<strong>on</strong><br />

Pers<strong>on</strong>al informati<strong>on</strong> about an organizati<strong>on</strong>’s pers<strong>on</strong>nel<br />

Teleph<strong>on</strong>e numbers, e-mail addresses, or general listings of staff unless necessary to<br />

fulfill organizati<strong>on</strong>al requirements<br />

Schedules of organizati<strong>on</strong>al principals or their exact locati<strong>on</strong> (whether <strong>on</strong> or off the<br />

premises)<br />

Informati<strong>on</strong> <strong>on</strong> the compositi<strong>on</strong>, preparati<strong>on</strong>, or optimal use of hazardous materials or<br />

toxins<br />

Sensitive informati<strong>on</strong> relating to homeland security<br />

Investigative records<br />

Financial records (bey<strong>on</strong>d those already publicly available)<br />

Medical records<br />

Organizati<strong>on</strong>’s physical and informati<strong>on</strong> security procedures<br />

Informati<strong>on</strong> about organizati<strong>on</strong>’s network and informati<strong>on</strong> system infrastructure<br />

Informati<strong>on</strong> that specifies or implies physical security vulnerabilities<br />

Plans, maps, diagrams, aerial photographs, and architectural plans of organizati<strong>on</strong>al<br />

building, properties, or installati<strong>on</strong>s<br />

Copyrighted material without the written permissi<strong>on</strong> of the owner<br />

Privacy or security policies that indicate the types of security measures in place to the<br />

degree that they may be useful to an attacker<br />

Establish an organizati<strong>on</strong>al-wide documented formal policy and process for<br />

approving public <strong>Web</strong> c<strong>on</strong>tent that—<br />

Identifies informati<strong>on</strong> that should be published <strong>on</strong> the <strong>Web</strong><br />

Identifies target audience<br />

Identifies possible negative ramificati<strong>on</strong>s of publishing the informati<strong>on</strong><br />

Identifies who should be resp<strong>on</strong>sible for creating, publishing, and maintaining this<br />

particular informati<strong>on</strong><br />

Provides guidelines <strong>on</strong> styles and formats appropriate for <strong>Web</strong> publishing<br />

Provides for appropriate review of the informati<strong>on</strong> for sensitivity and<br />

distributi<strong>on</strong>/release c<strong>on</strong>trols (including the sensitivity of the informati<strong>on</strong> in aggregate)<br />

E-4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!