WCF Security Guide：英文版Web服务安全指南

需积分: 3 120 浏览量更新于2024-07-27 收藏 3.55MB PDF 举报

"WCFSecurityGuide.pdf 是关于Windows Communication Foundation (WCF) 安全性的英文指南，提供了改进Web服务安全性的场景和实施指导。" 本文档深入探讨了微软的WCF（Windows Communication Foundation）框架的安全特性，这是一个用于构建分布式应用程序的服务模型。WCF允许开发者创建强类型、面向服务的应用，而安全是这类应用的关键组成部分。一、WCF安全基础 WCF安全主要关注以下方面： 1. **身份验证**：确定调用方的身份，确保只有授权的用户或服务可以访问资源。 2. **授权**：控制对服务操作的访问权限，基于调用方的身份或角色。 3. **数据完整性**：保证在传输过程中信息不被篡改。 4. **数据保密性**：确保敏感信息在传输时不被未授权的第三方查看。 5. **消息可靠性**：确保消息按顺序发送并到达目的地。 6. **事务支持**：在多步骤操作中提供原子性和一致性。二、WCF安全模式 WCF提供了多种安全模式，包括： 1. **Transport**模式：通过底层传输协议（如HTTPS）实现安全。 2. **Message**模式：在消息级别处理安全，允许更细粒度的控制。 3. **Transport with MessageCredential**模式：结合两者，传输层处理数据保密和完整性，消息头处理身份验证。三、安全绑定元素 WCF的安全功能由一系列绑定元素组成，如： - **TransportSecurityBindingElement**：用于实现传输层安全，如HTTPS。 - **MessageSecurityBindingElement**：用于处理消息级安全，例如XML-Security（WS-Security）标准。 - **UserNamePasswordBindingElement**：支持用户名和密码的身份验证。四、认证机制 WCF支持多种身份验证机制，包括： - **Windows集成认证**：利用操作系统级别的安全性。 - **证书**：基于X.509证书进行服务和客户端之间的安全通信。 - **用户名/密码**：简单的身份验证方式，但需要小心管理密码。 - **Kerberos**：企业环境中的高安全性认证。五、安全策略和配置通过配置文件（如web.config或app.config），开发者可以详细指定WCF服务的安全设置。这包括指定安全模式、身份验证类型、加密算法等。六、安全扩展性和自定义 WCF允许开发者创建自定义的安全令牌提供者、行为和绑定，以满足特定的安全需求或集成现有安全基础设施。七、安全最佳实践 1. **最小权限原则**：只给予服务和客户端必要的权限。 2. **定期更新证书**：避免证书过期导致的安全风险。 3. **使用SSL/TLS**：保护传输中的数据。 4. **启用审计**：记录安全事件，以便于故障排查和合规性检查。 WCFSecurityGuide.pdf 提供了全面的指导，帮助开发者理解和实施WCF服务的安全策略，确保Web服务的安全性。无论你是初学者还是经验丰富的开发者，这份文档都能提供宝贵的知识和实践经验。

• 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页未读，继续阅读

xiaoping55520

粉丝: 10
资源: 11

WCF Security Guide：英文版Web服务安全指南

WCFSecurityGuide

(源码)基于JavaWeb的饮品销售管理系统.zip

BitmapFunc.rar

c++课程设计-产品入库管理操作系统.zip

c语言火车票订票管理源码.rar

仿新浪微博下拉刷新继承FrameLayout.zip

浮动搜索框（SearchManager）.zip

(源码)基于ParticleTracker框架的传感器浮标系统.zip

python《树莓派使用OpenCV库实现人脸识别》+项目源码+文档说明

毕业设计&课设_基于 UserCF 与 CB 后融合的网络电视节目推荐系统（含多种技术，有详细实现步骤及数据处理）.zip

最新资源