|
|
Master SOA Design Pattern Catalog
|
|
|
|

Exception Shielding

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

|

Home > Service Security Patterns > Exception Shielding
|
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.
|
|
|
|
|
|


|
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 (Erl),
Service Perimeter Guard (Hogg, Smith, Chong, Hollander, Kozaczynski, Brader, Delgado, Taylor, Wall, Slater, Imran, Cibraro, Cunningham),
Utility Abstraction (Erl)
|

|
|
|
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.soabooks.com.
|
|