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

kind of supervision #13

Open
dlgdwy opened this issue Feb 26, 2024 · 1 comment
Open

kind of supervision #13

dlgdwy opened this issue Feb 26, 2024 · 1 comment

Comments

@dlgdwy
Copy link

dlgdwy commented Feb 26, 2024

I would like to ask what kind of supervision the ThreaTrace algorithm is? Is it self-supervised?

@robhta
Copy link

robhta commented Feb 27, 2024

I find the question interesting; I have already asked myself the same question, and my conclusion is that it depends on the perspective.
The authors themselves write that the unsupervised training mode of GraphSAGE is inappropriate for the task, and therefore, supervised training is used. In the discussion, the authors call the method unsupervised but describe it as semi-supervised.
Self-supervised fits as a description since the classification withholds information for learning derived from the original data.

Therefore:
A supervised setup is used in the training, but it gets by with information from the raw data, hence self-supervised training.
Regarding attack detection, the system manages without attack knowledge and can therefore be seen as Unsupervised Attack Detection.
I disagree least with Semi-Supervised (which is mentioned in the latest version of IEEE-Xplore), as I would think it learns with a few attack examples, which it does not.

Can you follow the reasoning? Comments and corrections are welcome!

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

2 participants