System, apparatus and method for anonymizing data prior to threat detection analysis
A computerized method involves obfuscating one or more segments of data that is part of a flow prior to analysis of the flow for malware. Each of the one or more obfuscated data corresponds to one or more anonymized data. Thereafter, an identifier is generated for each of the one or more anonymized data, and each identifier is substituted for its corresponding anonymized data. The anonymized data and its corresponding identifiers are separately maintained from the stored flow.
1. A computerized method for obfuscating, according to an obfuscation scheme, data that are part of a flow prior to analysis of the flow for malware, the method comprising:
generating a flow identifier for the flow;
identifying one or more personally identifiable information (PII) segments of data in the flow;
generating a data identifier for each of the one or more PII segments of data;
substituting each data identifier for a corresponding PII segment of data as part of the flow;
associating each data identifier with the flow identifier;
determining whether recovery of the one or more PII segments of data is desired;
anonymizing the PII segments of data, comprising:
encrypting PII segments of data for which recovery is desired with a first keying material, and
hashing PII segments of data for which recovery is not desired;
maintaining the anonymized PII segments of data and the corresponding data identifiers separately from the flow; and
responsive to changing the obfuscation scheme, decrypting the encrypted PII segments of data with the first keying material and reencrypt the decrypted PII segments of data with a second keying material without altering the corresponding data identifier or the flow.
2. The computerized method of claim 1 , wherein the maintaining the anonymized PII segments of data and the corresponding identifiers separately from the flow comprises storing the anonymized PII segments of data and the corresponding identifiers in a first region of memory and the flow, including non-anonymized data and the identifiers, in a second region of the memory.
3. The computerized method of claim 1 further comprising:
generating a second identifier for each of the one or more anonymized PII segments of data; and
maintaining the one or more anonymized PII segments of data and the corresponding second identifiers separately from the flow.
4. The computerized method of claim 3 , wherein the generating of the second identifier for each of the anonymized PII segments of data comprises generating a hash result for each of the anonymized PII segments of data.
5. The computerized method of claim 3 , wherein the maintaining the anonymized PII segments of data and the corresponding identifiers separately from the flow comprises storing the anonymized PII segments of data and the corresponding identifiers in a first region of a first memory, storing the anonymized PII segments of data and the corresponding second identifiers in a second region of a second memory, and the flow, including non-anonymized data and the identifiers, in a third region of the memory.
6. A data security system that obfuscates one or more segments of data that are part of a flow prior to analysis of the flow for malware, the system comprising:
a network sensor engine including processing circuitry that is configured to (i) generate a flow identifier for the flow, and (ii) identify one or more personally identifiable information (PII) segments of data in the flow; and
an analysis engine communicatively coupled to the network sensor engine, the analysis engine including processing circuitry that is configured to (i) generate a data identifier for each of the one or more PII segments of data, (ii) substitute each data identifier for a corresponding PII segment of data as part of the flow, associate the data identifiers with the flow identifiers, where the one or more PII segments of data and the corresponding data identifiers are stored separately from the flow, determine whether recovery of the one or more PII segments of data is desired, (iii) anonymize the PII segments of data, comprising encrypt PII segments of data for which recovery is desired with a first keying material, and hash PII segments of data for which recovery is not desired, and (iv) responsive to changing the obfuscation scheme decrypt the encrypted PII segments of data with the first keying material and reencrypt the decrypted PII segments of data with a second keying material without altering the corresponding data identifiers or the flow.
7. The data security system of claim 6 , the analysis engine storing the anonymized PII segments of data and the corresponding identifiers separately from the flow by storing the anonymized PII segments of data and the corresponding identifiers in a first region of memory and the flow, including non-anonymized data and the identifiers, in a second region of the memory.
8. The data security system of claim 6 , wherein the analysis engine is further configured to generate a second identifier for each of the anonymized PII segments of data, and maintain the anonymized PII segments of data and the corresponding second identifiers separately from the flow.
9. The data security system of claim 8 , wherein the analysis engine is configured to generate the second identifier for each of the anonymized PII segments of data, including generating a hash result for each of the PII segments of anonymized data.
10. The data security system of claim 8 , wherein the analysis engine is configured to maintain the anonymized PII segments of data and the corresponding identifiers separately from the flow by storing the anonymized PII segments of data and the corresponding identifiers in a first region of a first memory, storing the anonymized PII segments of data and the corresponding second identifiers in a second region of a second memory, and storing the flow, including non-anonymized data and the identifiers, in a third region of the memory.
11. A data security system that obfuscates one or more segments of data that are part of a flow prior to analysis of the flow for malware, the system comprising:
one or more processors; and
a memory communicatively coupled to the one or more processors, the memory including
a network sensor engine that is configured to (i) generate a flow identifier for the flow, and (ii) identify one or more personally identifiable information (PII) segments of data in the flow; and
an analysis engine communicatively coupled to the network sensor engine, the analysis engine being configured to (i) generate a data identifier for each of the one or more PII segments of data, (ii) substitute each data identifier for a corresponding PII segment of data as part of the flow, associate the data identifiers with the flow identifiers, and where the one or more PII segments of data and the corresponding data identifiers are stored separately from the flow, determine whether recovery of the one or more PII segments of data is desired, (iii) anonymize the PII segments of data, comprising encrypt PII segments of data for which recovery is desired with a first keying material, and hash PII segments of data for which recovery is not desired, and (iv) responsive to changing the obfuscation scheme decrypt the encrypted PII segments of data with the first keying material and reencrypt the decrypted PII segments of data with a second keying material without altering the corresponding data identifiers or the flow.