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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 19: Securing Your ASP.NET <strong>Application</strong> <strong>and</strong> <strong>Web</strong> Services 577At minimum, the account(s) must have the following permissions:●●●●●●Query key valueSet key valueCreate subkeyEnumerate subkeysNotifyReadFile AccessAny file that your application accesses must have an access control entry (ACE) inthe ACL that grants, at minimum, read access to the ASP.NET process account orimpersonated identity. Normally, ACLs are configured on the directory <strong>and</strong> the fileinherits the setting.In addition to using NTFS permissions to restrict access to files <strong>and</strong> directories, youcan also use ASP.NET trust levels to place constraints on <strong>Web</strong> applications <strong>and</strong> <strong>Web</strong>services to restrict which areas of the file system they can access. For example,Medium-trust <strong>Web</strong> applications can only access files within their own virtualdirectory hierarchy.For more information about ASP.NET CAS policy, see Chapter 9, “Using Code Access<strong>Security</strong> with ASP.NET.”ACLs <strong>and</strong> PermissionsThe ASP.NET process account <strong>and</strong>, for certain directories, any impersonationidentities (if your applications use impersonation) require the following NTFSpermissions. The permissions shown in Table 19.3 should be used in addition to anypermissions your applications might require to access application-specific file systemresources.

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

Saved successfully!

Ooh no, something went wrong!