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

[stateless validation] red team - blue team exercise #11142

Open
Tracked by #46
wacban opened this issue Apr 24, 2024 · 2 comments
Open
Tracked by #46

[stateless validation] red team - blue team exercise #11142

wacban opened this issue Apr 24, 2024 · 2 comments
Labels
A-stateless-validation Area: stateless validation Near Core

Comments

@wacban
Copy link
Contributor

wacban commented Apr 24, 2024

Create a dedicated network running stateless validation and schedule a week long session where the red team tries to hack and break it while the blue team tries to defend it.

The goals of this exercise are to find and later fix any vulnerabilites and bugs in stateless validation (red team) and to test detection and prevention systems (blue team). This can be considered a gamified internal security audit that gives developers the time and incentives to focus on the security aspects of the system.

@Ekleog-NEAR
Copy link
Collaborator

This is similar to the drill we had... last year? Two years ago?

I definitely think it's a good idea to have these with some regularity, the main questions being:

  • are we actually ready enough for it to have meaning?
  • do we have enough time on hand for this to make sense? (At least the red team will need to prepare before the drill, to have some attack ideas ready at least)

@wacban
Copy link
Contributor Author

wacban commented Apr 26, 2024

are we actually ready enough for it to have meaning?

Currently no, I created the issue in advance just to keep track of it. It's something that I'd love to see before mainnet release.

do we have enough time on hand for this to make sense?

That is yet to be seen :) Personally I think it's worth it both for the security insights and for the fun of it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-stateless-validation Area: stateless validation Near Core
Projects
None yet
Development

No branches or pull requests

2 participants