Policy Profile Composition

An individual Access Policy represents one decision. A Policy Profile brings together all decisions required for one protected service and produces the final rules file used by L2Proxy.

Assemble the complete protection profile

In Policy Profile Composer, an authorized engineer:

Figure — Policy profile to enforcement traceability across engineering artifacts and runtime evidence.

1. names and describes the profile;
2. selects the required Access Policies;
3. reviews their membership and evaluation order;
4. previews the complete assembled profile;
5. saves the Policy Profile.

Saving writes the final file into the L2Proxy rules location. The profile immediately becomes available for selection in Standalone Deployment and Operations. The customer does not need to manually combine separate policy files or move the resulting file between product components.

Manage profile contents

Policy Profile Manager provides a file-centered view of the saved profiles. It records:

• profile identity and description;
• member policies and their order;
• generated or customized status;
• final saved policy content;
• on-system rules-file location;
• revision, creation time, and update time;
• intended L2Proxy service context.

Profiles can be created, inspected, revised, regenerated, or removed under controlled management. Revising an individual Access Policy and revising a deployed Policy Profile remain deliberate, separate actions.

Handoff to service management

The saved Policy Profile is the controlled handoff from policy engineering to service operations. Standalone Deployment and Operations selects that profile for the required protected access path and runs it through an independent service instance. Policy composition remains in this chapter; service configuration, activation, supervision, and operating evidence are covered in Standalone Deployment and Operations.

Next: Industrial Policy Examples.