WCF安全实践：Web服务安全增强与实现指南

3星 · 超过75%的资源需积分: 3 46 浏览量更新于2024-07-29 收藏 3.55MB PDF 举报

“WCF安全指南WCFSecurityGuide.pdf”是关于改进Windows Communication Foundation (WCF)服务安全的文档，提供了场景分析和实现指导，旨在帮助开发者确保WCF应用的安全性。 WCF（Windows Communication Foundation）是微软.NET框架的一部分，用于构建面向服务的应用程序。它提供了一种模型来创建、配置和部署分布式通信服务，支持多种通信协议和数据格式。在WCF中，安全性是至关重要的，因为它涉及到数据保护、身份验证、授权以及消息完整性和机密性。本指南中可能涵盖的知识点包括： 1. **WCF安全模型**：WCF的安全模型基于SOAP消息安全，支持多种安全模式，如Transport、Message、TransportWithMessageCredential等。每种模式都有其特定的安全属性和应用场景。 2. **身份验证与授权**：讨论了如何配置WCF服务和客户端进行身份验证，包括使用Windows集成安全、证书、用户名/密码、智能卡等。此外，还会涉及角色基础的授权策略和自定义授权策略。 3. **消息加密**：解释如何使用SSL/TLS通过传输层加密数据，以及如何在消息级别使用XML加密确保数据的隐私。 4. **消息完整性与防篡改**：通过使用数字签名确保消息在传输过程中未被修改，防止中间人攻击。 5. **安全会话**：WCF支持安全会话，允许在多个请求之间保持安全连接，提供更高的性能和效率。 6. **互操作性**：讨论与其他Web服务标准（如WS-Security、WS-Trust等）的互操作性，以及如何配置WCF服务以与非WCF客户端或服务安全通信。 7. **安全配置**：详细说明如何在WCF配置文件中设置安全选项，包括绑定、行为和服务标识等。 8. **安全最佳实践**：提供实现安全WCF服务的建议，包括最小权限原则、安全更新和审计日志等。 9. **故障排除和调试**：介绍如何诊断和解决WCF安全相关的问题，如错误消息解析和使用WCF跟踪。 10. **案例研究和示例代码**：文档可能包含实际的安全场景分析和代码示例，帮助读者理解和应用所学概念。 “WCF安全指南”是开发人员和系统管理员深入了解和实施WCF服务安全的重要参考资料，有助于创建可靠且安全的分布式应用程序。遵循文档中的指导，可以确保你的WCF服务符合行业标准和最佳实践，有效防止潜在的安全威胁。

• Identity-based. Authorize users based on their identity.

• Claims-based. Grant or deny access to the operation or resources based on the client’s

claims.

• Resource-based. Protect resources using access control lists (ACLs).

• How to choose between trusted subsystem and impersonation/delegation

With the trusted subsystem model, you use the process identity to access downstream

network resources such as databases. With impersonation/delegation, you use

impersonation and use the original caller’s identity to access the database. The trusted

subsystem model offers better scalability because your application benefits from efficient

connection pooling. You also minimize back-end ACL management. Only the trusted

identity can access the database. Your end users have no direct access. In the trusted

subsystem model, the service is granted broad access to back-end resources. As a result, a

compromised service could potentially make it easier for an attacker to gain broad access

to back-end resources. Keeping the service account’s credentials protected is essential.

With impersonation/delegation, you benefit from operating system auditing because you

can track which users have attempted to access specific resources. You can also enforce

granular access controls in the database, and individual user accounts can be restricted

independently of one another in the database.

• How to choose between resource-based and role-based authorization

Your authorization strategy may also be influenced by your choice of authentication type.

Consider the following:

Resource-based authorization considerations:

• If you are using certificate authentication, you will need to map certificates to Windows

groups.

• If you are using username authentication, you will need to perform protocol transition.

• Windows authentication will work with resource-based authorization by default.

• Basic authentication will work with resource-based authorization by default.

Note: You need to impersonate for resource-based authorization.

Role-based authorization considerations:

• If you are using certificate authentication, you will need to map certificates to Windows

groups.

• If you are using username authentication with Windows groups, you will need to perform

protocol transition.

• Username authentication will work with ASP.NET roles by default.

• Windows authentication will work with Windows groups by default.

• Basic authentication will work with Windows groups by default.

Patterns

• How to leverage Web services security patterns

Improving Web Services Security: Scenarios and Implementation Guidance for WCF

Microsoft patterns & practices

Familiarize yourself with the following patterns, then evaluate and apply the patterns when

they make sense for your particular scenario:

• Brokered Authentication

• Brokered Authentication: Kerberos

• Brokered Authentication: X509 PKI

• Brokered Authentication: STS

• Data Confidentiality

• Data Origin Authentication

• Direct Authentication

• Exception Shielding

• Message Replay Detection

• Message Validator

• Perimeter Service Router

• Protocol Transition with Constrained Delegation

• Trusted Subsystem

For information on the patterns above, see the patterns & practices “Web Services Security”

guide at http://msdn.microsoft.com/en-us/library/aa480545.aspx.

Auditing and Logging

• How to enable auditing in WCF

You can enable auditing in the configuration file.

• How to instrument your WCF service

You can use ASP.NET Health Monitoring.

• How to improve your auditing in WCF

Audit for the following:

• User management events. Instrument your application and monitor user-management

events such as password resets, password changes, account lockout, user registration, and

authentication events. Doing this helps you to detect and react to potentially suspicious

behavior. It also enables you to gather operations data; for example, to track who is

accessing your application and when user account passwords need to be reset.

• Unusual or suspicious activity. Instrument your application and monitor events that

might indicate unusual or suspicious activity. This enables you to detect and react to

potential problems as early as possible. Unusual activity could include replays of old

authentication tickets or too many login attempts over a specific period of time.

• Significant business operations. Track significant business operations. For example,

instrument your application to record access to particularly sensitive methods and

business logic.

Improving Web Services Security: Scenarios and Implementation Guidance for WCF

Microsoft patterns & practices

Bindings

• How to choose the right WCF binding

Consider the following scenarios:

• If you need to support clients over the Internet, consider using wsHttpBinding.

• If you need to expose your WCF service to legacy clients such as an ASMX Web service,

use basicHttpBinding.

• If you need to support WCF clients within an intranet, consider using netTcpBinding.

• If you need to support WCF clients on the same machine, consider using

netNamedPipeBinding.

• If you need to support disconnected queued calls, use netMsmqBinding.

• If you need to support bidirectional communication between the WCF client and WCF

service, use wsDualHttpBinding or netTcpBinding.

• How to create a custom binding

To create a custom binding, in the WCF configuration file, select a set of binding elements

that are supposed to be constructed in a specific order. Those binding elements refer to

transaction, reliable message, security, encoding formats, and transport protocol.

• How to support multiple authentication and authorization strategies

Use multiple bindings to support multiple authentication and authorization strategies. For

instance, you could use basicHttpBinding with username authentication to support legacy

ASMX clients, and wsHttpBinding with Windows authentication to support newer WCF-

enabled clients.

Exception Management

• How to handle exceptions in WCF

Use fault contracts to handle exceptions in WCF. By using the FaultContract attribute in a

service contract, you can specify the possible faults that can occur in your WCF service. This

prevents you from exposing any other exception details to the clients.

• Apply the FaultContract attribute directly on a contract operation, specifying the

exception type that can be thrown as shown in the following example:

[OperationContract]

[FaultContract(typeof(DivideByZeroException))]

double Divide(double number1,double number2);

Impersonation / Delegation

• How to impersonate at the service level

You can impersonate the entire service by setting the impersonateCallerForAllOperations

attribute to "true" in the WCF configuration file. If you are impersonating all operations in

Improving Web Services Security: Scenarios and Implementation Guidance for WCF

Microsoft patterns & practices

the service, the Impersonation property of the OperationBehaviorAttribute applied to

each operation will override. Therefore if the property on the operation is set to something

other than Allowed or Required, impersonation will be turned off for that operation.

• How to impersonate at the operation level

You can impersonate declaratively by applying the OperationBehavior attribute on any

operation that requires client impersonation. Use impersonation selectively and only on the

operations that need it, since by nature impersonation increases the potential attack surface of

your application.

• How to flow the original caller to the back end (double hop)

If your WCF service runs under the Network Service account, configure your computer

account in Active Directory to be trusted for delegation. If your application runs under a

custom domain account, you must register a service principal name (SPN) in Active

Directory in order to associate the domain account with the HTTP service on your WCF

server. You then configure your domain account in Active Directory to be trusted for

delegation.

Impersonate the original caller imperatively or declaratively – before you access the back-

end resource, the original caller will be delegated to be authenticated and authorized at the

back end.

Message Validation

• How to perform parameter validation

Use parameter inspectors to validate for length, range, format, and type. You can validate

parameters on both the client and the service. The server should not trust client-side

validation, but you can use it to reduce round-trips for incorrect input. The following are the

key steps you need to perform:

1. Write a class that implements a parameter inspector.

2. Write class that implements endpoint behavior.

3. Write a class that implements a behavior element.

4. Add the behavior element as an extensibility point in the WCF configuration file.

5. Create an endpoint behavior that uses the behavior element as an extensibility point.

6. Configure the endpoint to use the endpoint behavior.

• How to perform message validation

Use schemas and regular expressions to validate for length, range, format, and type. Schemas

are preferred for validating complex types (classes and message contracts). For performance

reasons, you will want to load the schema from the cache (in the Message Inspector). You

can validate incoming and outgoing messages on the server side as well as incoming and

outgoing messages on the client side. The server should not trust client-side validation, but

you can use it to reduce round-trips for incorrect input.

The following are the key steps you need to perform:

1. Write a class that implements Message inspector.

2. Write a class that implements endpoint behavior.

Improving Web Services Security: Scenarios and Implementation Guidance for WCF

Microsoft patterns & practices

剩余688页未读，继续阅读

vision_n

粉丝: 3
资源: 21

WCF安全实践：Web服务安全增强与实现指南

WCF全面解析 上册.pdf

WCF全面解析 下册.pdf

WCF服务编程07.pdf

java .net wcf java.io.ioexception: stream closed

wcf接收uni.uploadFile的数据

Unity WCF插件

visual studio 部署wcf项目无svc文件

wcf接收uni.uploadFile的文件

vs wcf 更新接口

怎么使用POST 请求WCF服务

最新资源

WCF全面解析上册.pdf

WCF全面解析下册.pdf