Specifies the location where security-related event logs are written.
Assembly: System.ServiceModel (in System.ServiceModel.dll)
|Specifies the default location, which is determined by the operating system. If writing to the Security log is supported (such as on Windows Vista and Windows Server 2003 and later platforms), the default log location is the Security log. Otherwise (such as in Windows XP SP2), the default log location is the Application log.|
|Specifies the Application log in the event log.|
|Specifies the Security log in the event log. The calling thread must have SeAuditPrivilege to be able to write to the Security log.|
When creating a Windows Communication Foundation (WCF) application that requires authentication and/or authorization of callers, you can specify that events related to security be recorded for either success, failure, or both. The location of the log is determined by this enumeration.
The level of the audit log is specified by setting the MessageAuthenticationAuditLevel or the ServiceAuthorizationAuditLevel property of the ServiceSecurityAuditBehavior class to one of the AuditLevel values.
You can also specify audit behavior using the serviceSecurityAudit element binding.
If the AuditLogLocation property is set to and Audit Object Access is not set in the Local Security Policy, audit events will not be written to the Security log. No failure is returned, but audit entries will not be written to the Security log. In addition, the calling thread must have SeAuditPrivilege to be able to write to the Security log.
Default Dependent on Operating System
When setting the property to the value, the operating system determines which log will actually be written to. For more information, see Auditing Security Events.
Windows 7, Windows Vista, Windows XP SP2, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003
The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.