Securing a computing environment against malicious entities
The subject disclosure is directed towards securing network data traffic through a trusted partition of the computing environment. A proxy service may communicate transaction data from a client to security-critical code within the trusted partition, which compares the transaction data to a security policy from a commercial electronic entity. If the transaction data includes malicious content, a security component framework of the trusted partition may reject the transaction data and terminate communications with the client. If the transaction data does not include malicious content, the security component framework may communicate a secured version of the transaction data and retrieve response data from the commercial electronic entity, which may be further communicated back to the client.
1. A method performed at least in part on at least one processor and operative to secure network data traffic through a trusted partition of the computing environment, the method comprising:
processing transaction data directed to an untrusted partition of the computing environment via the trusted partition, the untrusted partition being associated with one or more commercial electronic entities;
comparing security policy information to the transaction data to identify blacklisted markup language content and to whitelist portions of the identified blacklisted markup language content necessary for completing a transaction associated with the transaction data;
modifying the transaction data to remove the identified blacklisted markup language content except for the whitelisted portions; and
communicating, via a secure communication channel, the modified transaction data to the untrusted partition.
2. The method of claim 1 , wherein comparing the security policy information to the transaction data further comprises removing HyperText Markup Language (HTML) elements matching regular expressions for blacklisted patterns.
3. The method of claim 1 further comprising terminating communications with any party to the transaction data that is in violation of the security policy information.
4. The method of claim 1 further comprising modifying response data provided by the one or more commercial electronic entities to include a complementary version of transaction status data.
5. The method of claim 1 , wherein using the security component framework further comprises generating secure response data without contacting the untrusted partition.
6. The method of claim 1 , wherein using the security component framework further comprises encrypting sensitive data being transmitted within the transaction data and replacing corresponding portions of the transaction data that comprise the sensitive data.
7. The method of claim 1 , wherein using the security component framework further comprises authenticating data entry points corresponding to the transaction data.
8. The method of claim 1 , wherein using the security component framework further comprises partitioning an electronic form document into a first portion comprising sensitive data entry points and a second portion comprising other data entry points.
9. The method of claim 1 further comprising executing an entity-specific security component of the security component framework on the transaction data.
10. The method of claim 1 , wherein communicating the response data further comprises returning entity-specific content based on the transaction data.
11. One or more computer-readable storage memory having computer-executable instructions stored thereon, which in response to execution by a computer, cause the computer to perform steps comprising:
processing a request form directed to a commercial electronic entity from a client computer, the request form comprising non-sensitive data and sensitive data;
returning information to the client computer and terminate a connection to the commercial electronic entity in response to a security policy violation associated with the request form;
if the request form satisfies a security policy, converting the request form into a secure request form with each sensitive data form field removed, communicating the secure request form to the commercial electronic entity, and using the sensitive data to complete a transaction with the commercial electronic entity; and
upon receiving response data from the commercial electronic entity, generating secure response data to include a complementary version of transaction status data and communicating the secure response data to the client computer.
12. The one or more computer-readable storage memory of claim 11 having further computer-executable instructions, which in response to execution by the computer, cause the computer to perform further steps comprising:
returning web content presenting the secure response data.
13. The one or more computer-readable storage memory of claim 11 having further computer-executable instructions, which in response to execution by the computer, cause the computer to perform further steps comprising:
computing a hash value for at least one portion of the request form and comparing the hash value to security policy to verify the request form.
14. The one or more computer-readable storage memory of claim 11 having further computer-executable instructions, which in response to execution by the computer, cause the computer to perform further steps comprising:
excluding regions of the request form from hash value computations.
15. The one or more computer-readable storage memory of claim 11 having further computer-executable instructions, which in response to execution by the computer, cause the computer to perform further steps comprising:
generating a secure communication channel with the client computer.
16. An apparatus, comprising:
an isolation mechanism, executing on hardware, configured to:
process transaction data directed to an untrusted partition of the computing environment via the trusted partition, the untrusted partition being associated with one or more commercial electronic entities;
compare security policy information to the transaction data to identify blacklisted markup language content and to whitelist portions of the identified blacklisted markup language content necessary for completing a transaction associated with the transaction data;
modify the transaction data to remove the identified blacklisted markup language content except for the whitelisted portions; and
communicate, via a secure communication channel, the modified transaction data to the untrusted partition.
17. The apparatus of claim 16 , wherein the isolation mechanism further configured to compare the security policy information to the transaction data further comprises removing HyperText Markup Language (HTML) elements matching regular expressions for blacklisted patterns.
18. The apparatus of claim 16 , wherein the isolation mechanism further configured to terminate communications with any party to the transaction data that is in violation of the security policy information.
19. The apparatus of claim 16 , wherein the isolation mechanism further configured to modify response data provided by the one or more commercial electronic entities to include a complementary version of transaction status data.
20. The apparatus of claim 16 , wherein the isolation mechanism further configured to generate secure response data without contacting the untrusted partition.