Implementation best practices

Skyflow’s implementation best practices help you make key architectural decisions around identity, monitoring, and connectivity when integrating Skyflow into your environment.

At Skyflow, we want your implementation to set you up for success from day one. Beyond the security best practices checklist, here are a few architectural decisions we recommend as you plan your integration.

• Implement SSO
  • Enable single sign-on for Studio instead of default username and password with MFA. SSO centralizes identity management within your existing identity provider and reduces credential sprawl across your organization.
  • Skyflow supports SSO through Okta, Auth0, Google Workspace, Azure AD, Ping, and more via SAML. For setup instructions, see Single sign-on.
• Stream audit logs to a SIEM
  • Stream audit logs to a SIEM for long-term retention, centralized security monitoring, and easier anomaly or abuse detection, extending well beyond the Audit Log API’s 90-day window.
  • Skyflow supports streaming audit logs to an AWS S3 bucket that feeds your SIEM. For setup instructions, see Audit logs and SIEM.
• Use Private Link connectivity
  • Connect to Skyflow through AWS PrivateLink or GCP Private Service Connect for fast, private connectivity that stays off the public internet end-to-end.
  • Private Link gives you:
    • Direct connectivity into your vault
    • A streamlined, simplified architecture without needing CDN
    • Rate limiting enforced at the vault level
  • For supported options, see the Private connectivity section of Deployment models.

Related

• Security best practices: Apply Skyflow’s full security checklist.
• Deployment models: Compare Skyflow’s deployment models and private connectivity options.
• Single sign-on: Configure SSO for Studio.
• Audit logs and SIEM: Stream audit logs to an AWS S3 bucket that feeds your SIEM.