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

Documentation: testing guide #21

Open
voltone opened this issue Nov 21, 2021 · 7 comments
Open

Documentation: testing guide #21

voltone opened this issue Nov 21, 2021 · 7 comments

Comments

@voltone
Copy link
Collaborator

voltone commented Nov 21, 2021

Create a 'testing guide' aimed at security professionals with little or no experience with the BEAM platform. The document should provide both background information, with links to relevant resources, and concrete examples of verification tests that show necessary hardening is in place.

Please add any suggestions for topics that we might cover as comments in this ticket.

@voltone
Copy link
Collaborator Author

voltone commented Nov 21, 2021

Erlang distribution protocol: overview, risks, EPMD, network interface binding, security mechanisms, TLS transport, ...

@voltone
Copy link
Collaborator Author

voltone commented Nov 21, 2021

Interaction with the host OS executables/processes: ports, os:cmd, NIFs, erl_child_setup, erlsrv, heart, ...

@voltone
Copy link
Collaborator Author

voltone commented Nov 21, 2021

Introspection: observer, crash dumps, remote console, to_erl

@voltone
Copy link
Collaborator Author

voltone commented Nov 21, 2021

Code loading: interactive vs. embedded, load paths, executable config files in Elixir releases, code_server

@varnerac
Copy link

Where to find config files. What files need restricted read/write permissions.

@vkatsuba
Copy link

Erlang/OTP profiling: fprof, eprof, cprof, dbg, lcnt, perf.

@vkatsuba
Copy link

Load testing - Tsung.

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

No branches or pull requests

3 participants