11.07.2015 Views

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

Improving Web Application Security: Threats and - CGISecurity

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.

Checklist: Securing ASP.NET 701Configuration File Settings (continued)Check DescriptionImpersonation identities (if used) are encrypted in the registry by using Aspnet_setreg.exe:Correct format of role names is verified.If multiple ASP.NET <strong>Web</strong> applications are deployed on the same <strong>Web</strong> server, the“IsolateApps” setting is used to ensure that a separate key is generated for each <strong>Web</strong>application.If the ASP. NET <strong>Web</strong> application is running in a <strong>Web</strong> farm, specific machine keys are used,<strong>and</strong> these keys are copied across all servers in the farm.If the view state is enabled, the validation attribute is set to “SHA1”.The validation attribute is set to “3DES” if the Forms authentication cookie is to beencrypted for the application.If mode=“StateServer”, then credentials are stored in an encrypted form in the registry byusing Aspnet_setreg.exe.If mode=“SQLServer”, then Windows authentication is used to connect to the state storedatabase <strong>and</strong> credentials are stored in an encrypted form in the registry by usingAspnet_setreg.exe.Unused file types are mapped to HttpForbiddenH<strong>and</strong>ler to prevent files from being retrievedover HTTP. For example:(continued)

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

Saved successfully!

Ooh no, something went wrong!