|
|
Master SOA Design Pattern Catalog
|
|
|
|

Message Screening

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

|

Home > Service Security Patterns > Message Screening
|
|
How can a service be protected from malformed or malicious input?
|
|
|
|
|

Problem

An attacker can transmit messages with malicious or malformed
content to a service, resulting in undesirable behavior.
|
|

Solution

The service is equipped or supplemented with special screening
routines that assume that all input data is harmful until proven
otherwise.
|
|

Application

When a service receives a message, it makes a number of checks
to screen message content for harmful data.
|
 |
 |
 |

Impacts

Extra runtime processing is required with each message
exchange, and the screening logic requires additional, specialized
routines to process binary message content, such as attachments.
It may also not be possible to check for all possible forms of
harmful content.
|
|
|
|
|
|


|
Because the service logic is equipped with extra message screening routines, malicious or malformed
data can still be detected and rejected before it has a chance to do harm.

|
|

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