- Help Center
- Troubleshooting & FAQs
- Training & references
-
Getting Started
-
Platform Overview
-
Scanning & Testing
-
Troubleshooting Asset Blockers
-
Vulnerability Management
-
Attack Surface Management
-
Continuous Threat Exposure Management (CTEM)
-
Integrations
-
Reporting
-
Security Best Practices
-
Advanced Features & Customizations
-
Troubleshooting & FAQs
-
Updates & Announcements
How Edgescan Handles Timezones
Edgescan handles timezones based on your own browser settings. Edgescan will default to UTC for all timezones outside of a browser.
Version Number: v1.0.0
Published Date: 2 Dec 2024
____________________________________________________________________________
Managing time zones effectively is essential for ensuring clarity and accuracy when dealing with global users. Edgescan addresses time zone complexities by providing consistent handling across its UI and API interactions.
UI Timezone Handling
- Default Storage in GMT+0: All timestamps are stored in GMT+0 to maintain consistency across the platform.
- Automatic Adjustment: When displayed in the browser, timestamps are automatically adjusted to match the user’s local time zone.
- For example, if an event is created at 11:00 AM GMT, a user in Los Angeles (PST) will see it as 3:00 AM.
API Timezone Handling
For API interactions, Edgescan provides flexibility:
- Default Timezone is GMT+0: All timestamps returned by the API are set to GMT+0, unless otherwise specified.
- Custom Timezone Support: A timezone parameter in the API requests adjusts the data to a specific timezone.
••If no timezone is specified, the response defaults to GMT+0.