Feature request: more frequent GeoIP database updates
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
- 6.8K All Categories
- 1.4K Nebula
- 29 Nebula Ideas
- 37 Nebula Status and Incidents
- 3.9K Security
- 200 Security Ideas
- 723 Switch
- 30 Switch Ideas
- 599 WirelessLAN
- 8 WLAN Ideas
- 4.5K Consumer Product
- 98 Service & License
- 214 New and Release
- 38 Security Advisories
- 512 FAQ
- 237 Nebula FAQ
- 117 Security FAQ
- 72 Switch FAQ
- Network Reliability
- Network Security
- IPTV
- Layer 3 Switching & Routing
- Surveillance / ONVIF
- Other Topics
- 65 WirelessLAN FAQ
- 5 Consumer Product FAQ
- Documents
- 30 Nebula Monthly Express
- 43 About Community
- 31 Security Highlight