Skip to content

Hi Skyflow team!

This is a sample of what your docs might look like on Starport, based on your public docs.

Take a look! Ask AI, search, the MCP server, and Markdown copies all work.

Starport is a free and open-source docs framework based on Starlight and maintained by Promptless. Promptless is the AI agent that automatically updates your customer-facing docs.

Every annual Promptless plan comes with white-glove migration to Starport, where we migrate the content, tune the result with you, and you own the repository so you're never locked in.

Book a 15-minute walkthrough

Sample migration of Skyflow docs to Starport, prepared by PromptlessBook 15-minute call

Skyflow | DocumentationSkyflow | DocumentationSkyflow | Documentation

Security best practices

Security Best Practices Checklist

Section titled “Security Best Practices Checklist”

Skyflow’s security best practices checklist helps you implement security measures to protect your data and ensure compliance with industry standards.

At Skyflow, we go above and beyond industry security requirements to ensure that your data is secure. Here is a checklist of our security best practices that you can use for your implementation.

  • IAM
    • Differentiate between user and applications accounts.
    • Ensure your service accounts and user permissions follow the principle of least privilege. In other words, give the lowest privileges possible so that access is granted only for necessary permissions.
    • Define personas and proper unique users and service accounts for usages.
    • Separate accounts for administration vs application runtime.
    • API keys don’t expire. In some instances, this is a convenience in terms of usability. However, the onus is on you and your partners or customers to protect the API key and monitor its usage securely.
    • For service accounts, set a reminder for the one-year credential expiration.
    • Secure service account credentials by storing them in designated secret stores with built-in security, and securely pass info to runtime applications (for example, by using environment variables).
  • Governance
    • Define proper governance policies for different functional roles and applications.
    • Create new custom roles as needed to specify exactly who gets which privileges.
    • Rotate service account keys before their expiration date.
  • Tokens
    • Secure your data tokens as if they were sensitive security data. In other words, allow only authenticated users, and use proper access control to restrict who can see which tokens on a need-to-know basis only.
    • If possible, use UUID4 format tokens to allow for maximum entropy. This is the Skyflow out-of-the-box option.
  • Integration
    • Use content security policy directives to secure content in SDK iframes.
  • Monitoring
    • Integrate the Skyflow Audit Log API into your SIEM to analyze and detect abuses or anomaly behavior.
  • Network
    • Provide network IPs of API clients or setup AWS PrivateLink, where applicable, to further restrict and secure data traffic.
  • IP allowlists
    • For any service account, Skyflow recommends configuring an IP allowlist to add an additional layer of security by limiting access to specific IP addresses or ranges.
    • Use Active - All for service accounts used by backend servers with static IP addresses, enforcing IP restrictions for bearer token generation and all API calls.
    • Use Active - Auth Only for service accounts used in client-side flows (such as Collect or Reveal), where the backend generates tokens from known IPs but end users access from dynamic IPs.
    • For more information, see IP allowlists overview.
↑↓ Select↵ Open