Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Acra, database protection suite #67

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

vixentael
Copy link

What is Acra?

Acra is a network encryption proxy to protect databases and database-based applications from data leaks, allowing greater security for distributed applications via cryptography and intrusion detection.

Acra has honeypot generation tool as part of suite, they call it "poison records". Poison records are the records specifically designed and crafted in such a way that they wouldn't be queried by a client application under normal circumstances. Yet poison records will be included in the outputs of SELECT * requests.

Upon passing AcraServer, they will inform it of untypical behaviour. The goal of using poison records is simple — to detect adversaries trying to download full tables / full database from the application server or trying to run full scans in their injected queries.

Acra is not only a honeypot generator

  • Acra allows to selectively encrypt sensitive records with strong multi-layer cryptography in client-side application. Client-side app doesn't have decryption key, thus compromising app won't lead to stealing key and decrypting data in the database.
  • Sensitive data is encrypted before being transmitted to the database, and decryption key is not stored on client side.
  • Data is decrypted in trusted environment (on AcraServer).
  • Acra allows to detect potential intrusions and SQL injections (using SQL firewall and poison records).
  • Works with PostgreSQL and MySQL databases.
  • Has SIEM integrations.
  • Suits for distributed, microservice-rich environments.
  • Has numerous examples and tutorials for many languages.
  • Allows your application to cover GDPR articles 25, 32, 33, 34.
  • Tested, supported, audited.

@vixentael
Copy link
Author

I think CI is failed because other link " 1. [L362] http://www.citi.umich.edu/u/provos/honeyd/ch01-results/1/ Cannot assign requested address - connect(2) for "www.citi.umich.edu" port 80 " is not accessible anymore.

@paralax can you take a look please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant