SOAPatterns.org

Overview
- Introduction
- History
- Acknowledgements
- Podcasts
- Candidate Patterns
- Forms
- Press Releases
- Resources
Compound Patterns
Design Patterns (alphabetical)
Design Patterns (by category)
- Foundational Inventory Patterns
- Logical Inventory Layer Patterns
- Inventory Centralization Patterns
- Inventory Implementation Patterns
- Inventory Governance Patterns
- Foundational Service Patterns
- Service Implementation Patterns
- Service Security Patterns
- Service Contract Design Patterns
- Legacy Encapsulation Patterns
- Service Governance Patterns
- Capability Composition Patterns
  - Capability Composition
  - Capability Recomposition
- Service Messaging Patterns
- Composition Implementation Patterns
- Service Interaction Security Patterns
- Transformation Patterns
- REST-inspired Patterns
Cloud Computing Patterns
Service Technology Specs
SOA School
- Home
- Matrix
- Certifications
- Courses
- Exams
- Self-Study Kits
- Workshops
- Licensing
- Online Store

Home > Design Patterns > Exception Shielding

Exception Shielding (Hogg, Smith, Chong, Hollander, Kozaczynski, Brader, Delgado, Taylor, Wall, Slater, Imran, Cibraro, Cunningham)

How can a service prevent the disclosure of information about its internal implementation when an exception occurs?

Problem

Unfiltered exception data output by a service may contain internal implementation details that can compromise the security of the service and its surrounding environment.

Solution

Potentially unsafe exception data is "sanitized" by replacing it with exception data that is safe by design before it is made available to consumers.

Application

This pattern can be applied at design time by reviewing and altering source code or at runtime by adding dynamic sanitization routines.

Impacts

Sanitized exception information can make the tracking of errors more difficult due to the lack of detail provided to consumers.

Principles

Service Abstraction

Architecture

Service

Potentially unsafe information is sanitized by routines added to the service logic, thereby releasing only safe exception information to service consumers.

Related Patterns in This Catalog

Service Agent, Service Perimeter Guard, Utility Abstraction

Related Service-Oriented Computing Goals

Increased Organizational Agility, Reduced IT Burden

This page contains excerpts from:

SOA Design Patterns by Thomas Erl

Foreword by Grady Booch

With contributions from David Chappell, Jason Hogg, Anish Karmarkar, Mark Little, David Orchard, Satadru Roy, Thomas Rischbeck, Arnaud Simon, Clemens Utschig, Dennis Wisnosky, and others.

(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)

For more information about this book, visit www.servicetechbooks.com.