Feature request: more frequent GeoIP database updates
Options
All Replies
-
Update after going online-reboot.I currently do not know if the "storage" where the GeoIP db is stored is:
- wiped or kept before reboot
- accessible from both firmware images (or as security feature, replicated in both images)
so if is needeed to reboot for whatever reason (firmware update, configuration rollback for instance?) I have no assurance I will capable of certify that the securty policies will be enforced as intended since the reboot with correct and updated data about the geoIP correlation.Also, allowing a scripted and/or a more frequent "check for update" of the geoIP db could restrict the timeframe of the staleness of the geoip data.As far as i know there's no "expected day" as for Microsoft patches for GeoIP updates. So if my device updates only monday at 5:am CET and the update of the db occours tuesday at 1 AM CET i'll have for six days the GeoIP db not fully updated with the modification published during tuesday.0 -
in general, the place for the update of the geo-ip database is not logical.why is it not under licencse -> signature update, as all other signatures also?and I agree with @mMontana, firmware update are a "problem", since they include all the signatures from the build time of the firmware. in worst case you are running for about 1 week with very old signatures.0
Categories
- All Categories
- 390 Beta Program
- 2.1K Nebula
- 116 Nebula Ideas
- 78 Nebula Status and Incidents
- 5.1K Security
- 51 USG FLEX H Series
- 247 Security Ideas
- 1.3K Switch
- 70 Switch Ideas
- 907 WirelessLAN
- 34 WLAN Ideas
- 5.9K Consumer Product
- 210 Service & License
- 332 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 1.9K FAQ
- 880 Nebula FAQ
- 415 Security FAQ
- 220 Switch FAQ
- 195 WirelessLAN FAQ
- 46 Consumer Product FAQ
- 137 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 72 About Community
- 63 Security Highlight