Autonomic

Using Immutable Service Containers, it is possible to implement a variety of autonomic security operations depending upon the implementation of the ISC and the architecture of the service deployed within it.  The following representative examples highlight a variety of component level operations (those specific to a single ISC) as well as architecture level operations (those performed across an ecosystem of ISCs).  It is expected that these and other use cases will evolve over time as additional experience is gained in their deployment.

''Note:  It is expected that there may be situations when an ISC Dock may provide persistent storage to its ISCs to preserve logs or other such information.  Conversely, an ISC may include a service or function to cache and/or store persistent content and state off-system.  Ultimately, the type of autonomic operations as well as the exact configuration and capabilities of the ISC Dock and ISC will vary based on individual site and product requirements.''

Component Level Operations

Component level operations are those restricted to a single Immutable Service Container.  Additional guidance and sample code will be provided for these operations as it is developed.

Self-Cleansing (Time-based)

Self-Cleansing (Event-based)

Self-Update (Time or Event-based)

Self-Rollback (Event-based)

Self-Quarantine (Event-based)

Self-Destruction (Event-based)

Self-Assessment (Time or Event-based)

Architecture Level Operations

Architecture level operations are those restricted to an ecosystem of Immutable Service Containers.

Genetic Replacement (Event-based)