Determine protective measure for data that meets criteria
AssigneeMicro Focus LLC
InventorsSasi Muthurajan, Matias Madou, Ronald J. Sechman, Jeremy Brooks
Life of this patent
Estimating the term…
Abstract
Example embodiments disclosed herein relate to determining whether a protective measure meeting criteria has been performed on data. Execution of an application under test (AUT) is monitored. A message that a field of the AUT should be considered sensitive is received. Data is determined to be entered into the field. The data is monitored during execution of the AUT to determine whether the protective measure that meets the criteria has been performed on the data.
Claims16
A non-transitory machine-readable storage medium storing instructions that, when executed by at least one processor of a device, cause the device to:
- monitor execution of an application under test (AUT) to execute on a server;
- receive, from a security test connected through a common communication channel, a message that a field of the AUT should be considered sensitive;
- determine data entered into the field of the AUT;
- determine that a protective measure is performed on the data;
- and
- determine whether the protective measure performed on the data meets a criteria,
- wherein to determine whether the protective measure meets the criteria, the instructions are to cause the device to:
- determine a type of the data;
- determine, based on the determined type of the data, a list of recommended protective measures for the data, the recommended protective measures corresponding to the determined type of the data;
- and
- determine whether the protective measure performed on the data meets the criteria based on the protective measure performed on the data being a recommended protective measure in the list of recommended protective measures,
- wherein the type of the data includes a first type of data that a user submits and is to be validated and a second type of data that the AUT is to retrieve on-demand, and
- wherein the list of recommended protective measures for the data of the first type includes hashing processes and the list of recommended protective measures for the data of the second type includes encryption processes.
A method comprising:
- monitoring execution, by at least one processor, of an application under test (AUT) to execute on a server;
- receiving, from a security test connected through a common communication channel, a message that a field of the AUT should be considered sensitive;
- determining data entered into the field of the AUT;
- monitoring the data during execution of the AUT;
- determining that the data is to be outputted;
- determining that a protective measure is performed on the data;
- and
- determining whether the protective measure performed on the data meets a criteria by:
- determining a type of the data;
- determining, based on the determined type of the data, a list of recommended protective measures for the data, the recommended protective measures corresponding to the determined type of the data;
- and
- determining whether the protective measure performed on the data meets the criteria based on the protective measure performed on the data being a recommended protective measure in the list of recommended protective measures,
- wherein the type of the data includes a first type of data that a user submits and is to be validated and a second type of data that the AUT is to retrieve on-demand, wherein the first type of data includes a password, a token, or a personal identification number (PIN) and the second type of data includes a credit card number or a social security number.
A system comprising:
- a server hosting an application under test (AUT);
- a runtime agent to monitor execution of the AUT;
- a computing device communicatively coupled to the AUT and the runtime agent through a common communication channel, the computing device to:
- determine that a field of the AUT should be considered sensitive;
- send a message to the runtime agent indicating that the field should be considered sensitive;
- enter data into the field,
- wherein the runtime agent is further to:
- receive the message and in response to receipt of the message, monitor the data during execution of the AUT to determine a protective measure performed on the data;
- and
- determine whether the protective measure performed on the data meets a criteria and provide the protective measure performed on the data to the computing device, wherein to determine whether the protective measure meets the criteria;
- determine a type of the data;
- determine, based on the determined type of the data, a list of recommended protective measures for the data, the recommended protective measures corresponding to the determined type of the data;
- and
- determine whether the protective measure performed on the data meets the criteria based on the protective measure performed on the data being a recommended protective measure in the list of recommended protective measures,
- wherein the type of the data includes a first type of data that a user submits and is to be validated and a second type of data that the AUT is to retrieve on-demand, and
- wherein the list of recommended protective measures for the data of the first type includes hashing processes and the list of recommended protective measures for the data of the second type includes encryption processes.
Dependencies are inferred from the claim text.