System and method for security planning with soft security constraints
AssigneeInternational Business Machines Corporation
InventorsKay Schwendimann Anderson, Pau-Chen Cheng, Trenton Ray Jaeger, Zhen Liu, Anton Viktorovich Riabov, Pankaj Rohatgi, Angela Schuett Reninger, Grant Wagner
Life of this patent
Estimating the term…
Abstract
A method for security planning with soft security constraints, include: receiving security-related requirements of a workflow to be developed using system inputs and processing components; and generating at least one proposed workflow according to the security-related requirements, wherein the at least one proposed workflow satisfies soft constraints.
Claims21
A method for security planning with soft security constraints, comprising:
- receiving security-related requirements of a workflow to be developed using system inputs and processing components;
- and
- generating at least one proposed workflow according to the security-related requirements, wherein the at least one proposed workflow satisfies soft constraints.
A computer program product comprising a computer useable medium having computer program logic recorded thereon for security planning with soft security constraints, the computer program logic comprising:
- program code for receiving security-related requirements of a workflow to be developed using system inputs and processing components;
- and
- program code for generating at least one proposed workflow according to the security-related requirements, wherein the at least one proposed workflow satisfies soft constraints.
A method for security planning with security constraints, comprising:
- receiving from a user security-related requirements of a workflow to be developed using system inputs and processing components;
- constructing a planning task description based on the security-related requirements;
- invoking a planner to build at least one workflow based on the planning task description;
- constructing a user-accessible description of the at least one workflow;
- presenting the user-accessible description to the user;
- receiving a workflow selection from the user;
- recording information associated with the workflow selection;
- and
- executing the selected workflow.
Dependencies are inferred from the claim text.