You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please replace every line in curly brackets { like this } with appropriate answers, and remove this line.
Problem to Solve
We use it for selecting observable at SOC level.
Some observables correspond to legitimate IP addresses, domain names, etc. Their use in consuming devices will generate false positive.
Some observables might be 'malicious' for sometimes.
The rating/scoring will indicate 'how malicious' a give observable is.
Current Workaround
N/A
Proposed Solution
Scoring/rating: numerical value associated to each observable.
Range: [0-100]
(0: non malicious)
(100: malicious)
The logic to calculate or set the rating can be different depending on the organisation.
It should be subject to a separate 'issue'
Additional Information
N/A
The text was updated successfully, but these errors were encountered:
A score is now computed at the observable level and based on a new attribute "score" attached to the relations of type "indicates" that relates observables to threats.
Please replace every line in curly brackets { like this } with appropriate answers, and remove this line.
Problem to Solve
We use it for selecting observable at SOC level.
Some observables correspond to legitimate IP addresses, domain names, etc. Their use in consuming devices will generate false positive.
Some observables might be 'malicious' for sometimes.
The rating/scoring will indicate 'how malicious' a give observable is.
Current Workaround
N/A
Proposed Solution
Scoring/rating: numerical value associated to each observable.
Range: [0-100]
(0: non malicious)
(100: malicious)
The logic to calculate or set the rating can be different depending on the organisation.
It should be subject to a separate 'issue'
Additional Information
N/A
The text was updated successfully, but these errors were encountered: