提升Web服务安全：认证、授权与通信设计

需积分: 9 20 浏览量更新于2024-07-22 收藏 3.55MB PDF 举报

"提高Web服务安全性：使用WCF的解决方案模式和安全方面改进的原则、模式和实践" 在Web服务开发中，确保服务的安全性是至关重要的。"提高Web服务安全性"这个主题聚焦于如何通过有效的方式来保护你的服务，包括认证、授权和通信设计等多个关键领域。以下是对这些知识点的详细说明： 1. **认证（Authentication）**：认证是确定调用服务的用户或系统身份的过程。对于Web服务，常见的认证机制包括基本认证、摘要认证、Windows NTLM/Kerberos认证和证书认证。使用WCF（Windows Communication Foundation），你可以配置服务以支持多种认证模式，并根据安全需求选择合适的方案。 2. **授权（Authorization）**：授权决定了认证过的实体可以执行哪些操作。在WCF中，可以通过角色基础授权或自定义策略来控制访问权限。例如，你可以设置权限级别，只允许特定角色的用户访问特定的服务操作。 3. **通信设计（Communication Design）**：安全的通信设计涉及到数据加密、完整性保护和消息源验证。WCF提供了多种绑定元素，如HTTPS、TransportWithMessageCredential等，用于加密传输层和消息层。此外，还支持SSL/TLS协议以确保网络通信的安全。 4. **解决方案模式（Solution Patterns）**：对于常见的分布式应用场景，WCF提供了一系列预定义的解决方案模式，如面向服务的架构（SOA）、企业服务总线（ESB）和微服务架构。这些模式可以帮助开发者应对复杂的安全挑战，如服务间的信任建立、事务管理以及错误处理。 5. **原则、模式和实践（Principles, Patterns, and Practices）**： - 原则：如最小权限原则，意味着服务账户应具有完成其任务所需的最低权限。 - 模式：如双因素认证、安全令牌服务等，是解决安全问题的标准化方法。 - 实践：例如定期更新和审核安全策略，对敏感数据进行加密，以及实施入侵检测和防御系统。 6. **知识产权和法律考虑（Intellectual Property and Legal Considerations）**：在实现这些安全措施时，必须遵守适用的版权法律，并尊重微软和其他可能拥有相关专利、商标、版权或其他知识产权的权利。 7. **持续更新和适应性（Up-to-date and Adaptability）**：文档中的信息可能会随时间变化，因此开发者需要定期检查最新的安全指南，以应对不断演变的威胁和攻击技术。提高Web服务安全性是一个综合性的过程，需要结合认证、授权、通信设计等多个方面进行深入理解和实践。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页未读，继续阅读

shawn_tao

粉丝: 0
资源: 1

提升Web服务安全：认证、授权与通信设计

building restful web services with spring 5 2e

Host Your Web Site In The Cloud: Amazon Web Services Made Easy

HTTP Strict Transport Security (HSTS) not implemented

nginx proxy-

android hal selinux

AWS Global Accelerator

threat intelligence

基于SpringBoot和Vue的Web设计与实现外文文献

nginx + fastapi

最新资源