Granted Patent B2

US 12,524,558 · App. 17/859,693 · Granted Jan 13, 2026

Inventors: Marcelo Yannuzzi (Vufflens-la-Ville, CH); Hervé Muyal (Gland, CH); Jean Andrei Diaconu (Haute-Savoie, FR); Frank Brockners (Cologne, DE); Carlos Goncalves Pereira (Carlsbad, CA)

Assignee: Cisco Technology, Inc.

G06F21/62G06F9/543G06F21/6209

Abstract

Claims (41)

1 . A method comprising:

obtaining, by a device, program code of an application that defines annotations denoting a plurality of data types handled by the application;

determining, by the device and for each of the plurality of data types, an association between that data type and a category of sensitive data;

creating, by the device and based on the association for each of the plurality of data types, a protection binding that defines a data handling scope bonded to the association between that data type and its associated category of sensitive data; and

causing, by the device, data compliance policies to be applied to the application according to its corresponding associations and protection bindings, wherein at least one of the data compliance policies controls how a particular category of sensitive data is stored, accessed, or processed by the application within one or more designated processing environments that are determined based on the category of sensitive data.

2 . The method as in claim 1 , wherein the association is defined by a programmer via a user interface or an application programming interface.

3 . The method as in claim 1 , wherein the device automatically infers the association from a corresponding annotation of the annotations in the program code.

4 . The method as in claim 1 , further comprising:

associating, by the device, a token having a predefined access scope with a particular category of sensitive data.

5 . The method as in claim 1 , wherein at least one of the data compliance policies controls where a particular category of sensitive data is stored by the application.

6 . The method as in claim 1 , wherein at least one of the data compliance policies controls how a particular category of sensitive data is accessed by the application.

7 . The method as in claim 1 , wherein at least one of the data compliance policies controls where a workload of the application that is associated with a particular category of sensitive data is executed.

8 . The method as in claim 1 , further comprising:

associating, by the device, a pointer to an encryption key with a particular category of sensitive data.

9 . The method as in claim 1 , further comprising:

automatically generating, by the device, data compliance constraints based on a type of the application or where the application will be deployed.

10 . The method as in claim 9 , wherein the device automatically generates the data compliance constraints based on a repository of industrial regulations, governmental regulations, or organizational regulations.

11 . An apparatus, comprising:

one or more network interfaces;

a processor coupled to the one or more network interfaces and configured to execute one or more processes; and

a memory configured to store a process that is executable by the processor, the process when executed configured to:

obtain program code of an application that defines annotations denoting a plurality of data types handled by the application;

determine, for each of the plurality of data types, an association between that data type and a category of sensitive data;

create, based on the association for each of the plurality of data types, a protection binding that defines a data handling scope bonded to the association between that data type and its associated category of sensitive data; and

cause data compliance policies to be applied to the application according to its corresponding associations and protection bindings, wherein at least one of the data compliance policies controls how a particular category of sensitive data is stored, accessed, or processed by the application within one or more designated processing environments that are determined based on the category of sensitive data.

12 . The apparatus as in claim 11 , wherein the association is defined by a programmer via a user interface or an application programming interface.

13 . The apparatus as in claim 11 , wherein the apparatus automatically infers the association from a corresponding annotation of the annotations in the program code.

14 . The apparatus as in claim 11 , wherein the process when executed is further configured to:

associate a token having a predefined access scope with a particular category of sensitive data.

15 . The apparatus as in claim 11 , wherein at least one of the data compliance policies controls where a particular category of sensitive data is stored by the application.

16 . The apparatus as in claim 11 , wherein at least one of the data compliance policies controls how a particular category of sensitive data is accessed by the application.

17 . The apparatus as in claim 11 , wherein at least one of the data compliance policies controls where a workload of the application that is associated with a particular category of sensitive data is executed.

18 . The apparatus as in claim 11 , wherein the process when executed is further configured to:

automatically generate data compliance constraints based on a type of the application or where the application will be deployed.

19 . The apparatus as in claim 18 , wherein the process when executed is further configured to:

automatically generate the data compliance constraints based on a repository of industrial regulations, governmental regulations, or organizational regulations.

20 . A tangible, non-transitory, computer-readable medium storing program instructions that cause a device to execute a process comprising:

obtaining, by the device, program code of an application that defines annotations denoting a plurality of data types handled by the application;

determining, by the device and for each of the plurality of data types, an association between that data type and a category of sensitive data;

creating, by the device and based on the association for each of the plurality of data types, a protection binding that defines a data handling scope bonded to the association between that data type and its associated category of sensitive data; and

causing, by the device, data compliance policies to be applied to the application according to its corresponding associations and protection bindings, wherein at least one of the data compliance policies controls how a particular category of sensitive data is stored, accessed, or processed by the application within one or more designated processing environments that are determined based on the category of sensitive data.

Assignments (1)

Continuity (1)

References Cited (37)