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

Records of the same Alert family must be alike #8331

Closed
DGabri opened this issue Apr 13, 2024 · 0 comments
Closed

Records of the same Alert family must be alike #8331

DGabri opened this issue Apr 13, 2024 · 0 comments
Assignees

Comments

@DGabri
Copy link
Contributor

DGabri commented Apr 13, 2024

The API: /lua/alert_stats.lua format=json is not consistent. This causes parsing problems. The json key in question is 'flow_related_info'.

This is an example of suspicious DNS Traffic api response content with mismatching response:

  • Alert x response: {'descr': {'client_traffic': '151', 'server_traffic': '173'}}
  • Alert k response: {'descr': {'last_query_type': 'A',
    'server_traffic': '159',
    'last_return_code': 'NOERROR',
    'last_query': [VALUE OMITTED FOR THIS GITHUB ISSUE],
    'client_traffic': '143'}}

Here an example of binary application transfer:

  • Alert x response: {'descr': {'client_traffic': '418', 'server_traffic': '34588'}}
  • Alert k response: {'descr': {'last_user_agent': 'AutoIt',
    'last_url': [VALUE OMITTED FOR THIS GITHUB ISSUE],
    'http_info': 'GET',
    'client_traffic': '21629',
    'server_traffic': '798426',
    'last_return_code': 200}}
@lucaderi lucaderi changed the title Records of the same Alert family must be the same Records of the same Alert family must be alike May 8, 2024
@lucaderi lucaderi assigned MatteoBiscosi and NicoMaio and unassigned lucaderi May 8, 2024
@DGabri DGabri closed this as completed May 8, 2024
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

4 participants