Getting Started
This guide will help you get started with Alien Giraffe and understand how to leverage it to provision secure and auditable access to multiple data sources.
- WHO: Humans or Systems needs to access data.
- WHAT: Data that is stored in Databases and Object Storage, with sources and datasets catalogued by criticality
- WHEN: Time and for how long do they need to access the data.
- WHERE: Channel and format the data will be accessed: SQL socket, API, Web UI
- WHY: Customer Support, Platform Incident, Internal escalations, Triagging, Debugging, Application
Components
Section titled “Components”Alien Giraffe is built around six core components that work together to provide secure, auditable data access. Each component implements a specific aspect of the 5 W’s framework.
Policies
Section titled “Policies”Define declarative access rules by coordinating the five core components. Policies are version-controlled YAML/JSON files that centralize access control by specifying subjects, resources, constraints, channels, and context in a single definition.
Subjects (WHO)
Section titled “Subjects (WHO)”Define who can access data through identity management, authentication, and team-based access control. Subjects represent users, teams, service accounts, and applications. Policies reference subjects to specify who is authorized.
Resources (WHAT)
Section titled “Resources (WHAT)”Connect and catalog your databases, object storage, and data warehouses. Resources are registered with connection details, credentials, and classification metadata. Policies reference resources to specify what data can be accessed.
Constraints (WHEN)
Section titled “Constraints (WHEN)”Provide temporal controls for when and how long access is granted. Constraints manage time windows, session durations, approval timeouts, and just-in-time access patterns. Policies reference constraints to set temporal boundaries.
Learn more about Constraints →
Channels (WHERE)
Section titled “Channels (WHERE)”Control where and how data is accessed through SQL connections, APIs, web interfaces, and application integrations. Channels manage access pathways and methods. Policies reference channels to specify access operations.
Context (WHY)
Section titled “Context (WHY)”Provide purpose, justification, and organizational context through identity providers, HR systems, and compliance platforms. Context supplies user identities, team memberships, and employment data. Policies reference context to require justification.
Next Steps
Section titled “Next Steps”Now that you understand the core components of Alien Giraffe, here’s how to get started:
- Install Alien Giraffe - Follow the installation guide
- Configure your first data source - See sources configuration
- Create your first policy - Learn about policy writing
- Set up identity integration - Connect your identity provider
- Monitor and audit - Explore monitoring and logging
For more detailed information, check out our component documentation or explore the guides for step-by-step tutorials.