Audit Logs

migVisor employs audit logging to detect unauthorized activities and provide accountability for migVisor personnel. Audit logs capture details about system configuration changes and access events, with details to identify who was responsible for the activity, when and where the activity took place, and what the outcome of the activity was.

GCP

By default, system events are logged for GCP services. User access is logged via API logging.

Admin Activity and System Event audit logs are always written and can't be configured, excluded, or disabled.

Data Access audit logs are configured for relevant Google services, such as Cloud SQL, FireStore, Cloud Storage, Compute Engine API, Cloud DNS API, Service Usage API, and IAM API.

Additionally, VPC flow logs and Cloud DNS query logs are enabled.

API invocations are stored in FireStore. Additional flow logs are written into the GCP Logging service. Each log also contains information about the current session.

Azure

By default, system events are logged for Azure services. User access is logged via API logging.

Application and System Event audit logs are always written and can't be configured, excluded, or disabled.

Data Storage audit logs are configured for relevant Azure services.

API invocations are stored in the application log. Additional flow logs are written into the Azure Log Analytics service. Each log also contains information about the current session.

All logs are stored for periods between 1 and 2 years, depending on the nature of the data and type of usage.