The NOAA web sites have been inundated by malicious bots over the past few months. We are concerned that that our data will differ significantly from the DAP data as we do our best to filter out the bots (where possible). We are using the following criteria:
Evaluation Risk Weighting
The tool calculates the probability of malicious activity based on five key technical dimensions.
| Dimension |
Threshold |
Details |
Significance |
| Language |
Greater than 45% |
Language is not English |
Detection of non-standard or mismatching browser language settings. |
| Source |
Greater than 40% |
Source and medium are not available |
Analysis of traffic origin and referral strings. |
| Country |
Greater than 60% |
Country is not United States |
High-volume clusters from non-standard geographic regions. |
| Operating System |
Greater than 10% |
Outdated Operating System |
Use of outdated or uncommon OS versions (e.g., Macintosh Intel 10.15). |
| Screen Resolution |
Greater than 1% |
Screen resolution is square |
Detection of headless browser signatures (e.g., 1366x1366). |
We were wondering if something like this could be implemented as an optional filter for DAP data - at least for NOAA?
The NOAA web sites have been inundated by malicious bots over the past few months. We are concerned that that our data will differ significantly from the DAP data as we do our best to filter out the bots (where possible). We are using the following criteria:
Evaluation Risk Weighting
The tool calculates the probability of malicious activity based on five key technical dimensions.
We were wondering if something like this could be implemented as an optional filter for DAP data - at least for NOAA?