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

Ensure Balance Tracker and Payment Finality #675

Open
sappenin opened this issue Oct 26, 2020 · 0 comments
Open

Ensure Balance Tracker and Payment Finality #675

sappenin opened this issue Oct 26, 2020 · 0 comments
Labels
v1.0 Features to be fixed for a 1.0 release

Comments

@sappenin
Copy link
Collaborator

We should put more thought into how to prove balance-tracker and payment finality in the Connector layer. E.g., potentially there is an infrastructure/deployment best-practice that we should identify. More research required here.

Potentially a doc on https://interledger4j.dev with recs:

Recommendations

  1. Enable auditing in Postgres (every update should have a user).
  2. Force all users to login with a personal identity.
  3. Stream all packets to BigQuery to prevent
  4. Put audit records into different namespace/db than transactional data.
  5. Use external logging tool
  6. Good fraud detection systems (potentially ML to detect irregularities).
  7. Limits on settlement engine amounts.
  8. Good network segmentation/isolation for various systems.
  9. User-facing limits on withdrawals (amounts, waiting periods, etc).
  10. Regular audits (external + internal)

Types of attack to consider

  1. External Application layer
  2. Internal infra compromise.
  3. Sysadmin Attacks
@sappenin sappenin added the v1.0 Features to be fixed for a 1.0 release label Feb 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1.0 Features to be fixed for a 1.0 release
Projects
None yet
Development

No branches or pull requests

1 participant