moai-adk 0.8.0__py3-none-any.whl → 1.1.0__py3-none-any.whl

moai_adk/templates/.claude/skills/moai-platform-auth0/modules/gdpr-compliance.md

@@ -0,0 +1,313 @@
+# GDPR Compliance
+
+The General Data Protection Regulation (GDPR) is a comprehensive EU data protection law. Auth0 provides features and documentation to support customer compliance obligations.
+
+## GDPR Overview
+
+### Applicability
+
+GDPR applies to:
+- Companies processing EU resident personal data
+- Companies established in the EU
+- Non-EU companies monitoring EU individuals
+- Non-EU companies offering services to EU
+
+### Core Principles
+
+Lawfulness, Fairness, Transparency:
+- Legal basis for processing
+- Clear communication to users
+- Honest data practices
+
+Purpose Limitation:
+- Collect for specified purposes
+- Not use beyond stated purposes
+- Document processing purposes
+
+Data Minimization:
+- Collect only necessary data
+- Avoid excessive collection
+- Regular data review
+
+Accuracy:
+- Keep data accurate
+- Enable correction
+- Regular updates
+
+Storage Limitation:
+- Retain only as needed
+- Define retention periods
+- Regular deletion
+
+## Auth0's Role
+
+### Data Processor
+
+Auth0 functions as Data Processor:
+- Processes data on customer instructions
+- Follows service agreement terms
+- Provides processing documentation
+
+### Data Controller
+
+Customer functions as Data Controller:
+- Determines processing purposes
+- Decides what data to collect
+- Manages user consent
+
+### Responsibility Division
+
+Auth0 Responsibilities:
+- Secure data processing
+- Breach notification
+- Processing documentation
+- Data export tools
+- Deletion capabilities
+
+Customer Responsibilities:
+- Define processing purposes
+- Obtain user consent
+- Handle user requests
+- Comply with regulations
+
+## User Rights
+
+### Right of Access
+
+Users can request:
+- Confirmation of processing
+- Copy of their data
+- Processing information
+
+Implementation:
+- Use Management API
+- Export user data
+- Provide in machine-readable format
+
+### Right to Rectification
+
+Users can request:
+- Correction of inaccurate data
+- Completion of incomplete data
+
+Implementation:
+- Dashboard user management
+- Management API updates
+- User profile editing
+
+### Right to Erasure (Right to be Forgotten)
+
+Users can request:
+- Deletion of their data
+- In certain circumstances
+
+Implementation:
+- Dashboard user deletion
+- Management API deletion
+- Removes profile and metadata
+
+### Right to Data Portability
+
+Users can request:
+- Data in structured format
+- Machine-readable format
+- Transfer to another service
+
+Implementation:
+- Export as JSON
+- Management API export
+- Standard format
+
+## Implementation
+
+### Consent Management
+
+Collecting Consent:
+- Implement consent checkboxes
+- Lock widget integration
+- Custom form implementation
+
+Tracking Consent:
+- Store in user metadata
+- Record consent timestamp
+- Document consent version
+
+Consent Withdrawal:
+- Provide withdrawal mechanism
+- Process withdrawal promptly
+- Update processing accordingly
+
+### Data Access Requests
+
+Handling Requests:
+1. Verify user identity
+2. Retrieve user data
+3. Format in portable format
+4. Deliver to user
+
+Data Sources:
+- User profile
+- User metadata
+- App metadata
+- Connection data
+
+### Data Deletion
+
+Deletion Process:
+1. Verify user identity
+2. Confirm deletion request
+3. Delete via dashboard or API
+4. Confirm deletion complete
+
+What's Deleted:
+- User profile
+- User metadata
+- App metadata
+- Associated data
+
+### Data Portability
+
+Export Format:
+- JSON format
+- Machine-readable
+- Standard structure
+
+Export Content:
+- Profile information
+- Metadata
+- Connection info
+
+## Security Measures
+
+### Technical Safeguards
+
+Profile Encryption:
+- Data encrypted at rest
+- Encrypted in transit
+- Key management
+
+Access Controls:
+- Role-based access
+- Audit logging
+- Least privilege
+
+### Security Features
+
+Breach Detection:
+- Breached password detection
+- Anomaly detection
+- Attack protection
+
+Authentication Security:
+- Multi-factor authentication
+- Step-up authentication
+- Strong password policies
+
+Brute Force Protection:
+- Account protection
+- IP throttling
+- Bot detection
+
+## Best Practices
+
+### Before Implementation
+
+Assessment:
+- Identify personal data collected
+- Document processing purposes
+- Establish legal basis
+- Plan consent mechanism
+
+Configuration:
+- Enable security features
+- Configure data retention
+- Set up audit logging
+- Plan for user requests
+
+### During Operation
+
+Ongoing Practices:
+- Regular data review
+- Consent management
+- Request handling procedures
+- Security monitoring
+
+Documentation:
+- Processing activities
+- Security measures
+- Request logs
+- Consent records
+
+### Staff Training
+
+Required Knowledge:
+- GDPR basics
+- User rights
+- Request handling
+- Security practices
+
+### Incident Response
+
+Breach Procedures:
+- Detection mechanisms
+- Response procedures
+- Notification requirements
+- Documentation
+
+## Auth0 Features for GDPR
+
+### Dashboard Capabilities
+
+User Management:
+- View user data
+- Edit user profiles
+- Delete users
+- Export data
+
+Audit Logs:
+- User activities
+- Admin actions
+- Access tracking
+
+### API Capabilities
+
+Management API:
+- User CRUD operations
+- Bulk operations
+- Data export
+- Metadata management
+
+### Compliance Tools
+
+Data Processing:
+- Documentation available
+- DPA available
+- Sub-processor list
+
+Security:
+- Certifications (ISO, SOC 2)
+- Security practices
+- Incident response
+
+## Documentation Requirements
+
+### Required Records
+
+Processing Activities:
+- Categories of data
+- Processing purposes
+- Data recipients
+- Retention periods
+
+Security Measures:
+- Technical controls
+- Organizational measures
+- Access controls
+
+### Customer Documentation
+
+Maintain Records Of:
+- User consent
+- Data access requests
+- Deletion requests
+- Security incidents

moai_adk/templates/.claude/skills/moai-platform-auth0/modules/guardian-configuration.md

@@ -0,0 +1,269 @@
+# Auth0 Guardian Configuration
+
+Auth0 Guardian is a mobile application for iOS and Android enabling multi-factor authentication through push notifications and one-time passwords.
+
+## Overview
+
+Guardian provides two primary authentication methods:
+- Push Notifications: Users receive push notifications and approve with one tap
+- One-Time Passwords (OTP): 6-digit codes valid for 30 seconds
+
+## Mobile Application
+
+### Supported Platforms
+
+iOS:
+- Available on App Store
+- Supports Face ID and Touch ID
+- Passcode protection available
+
+Android:
+- Available on Google Play Store
+- Fingerprint authentication support
+- PIN protection available
+
+### App Features
+
+Security Settings:
+- 6-digit PIN protection
+- Biometric authentication (Face ID, Touch ID, fingerprint)
+- Secure storage of enrollment data
+
+Language Support:
+- 50+ languages and dialects
+- User-selectable language preference
+- Localized notifications
+
+Customization:
+- Custom application name display
+- Branded accent colors
+- Custom app icons
+
+## Push Notification Configuration
+
+### Notification Delivery Services
+
+AWS Simple Notification Service (SNS):
+- Configure AWS credentials
+- Set up SNS topics
+- Handle delivery to both platforms
+
+Firebase Cloud Messaging (FCM):
+- Android notification delivery
+- Configure Firebase project
+- Server key configuration
+
+Apple Push Notification (APN):
+- iOS notification delivery
+- Certificate or key-based authentication
+- Configure bundle identifier
+
+### Enrollment Flow
+
+1. User authenticates with primary credentials
+2. Universal Login presents QR code
+3. User scans QR code with Guardian app
+4. App registers with Auth0
+5. Enrollment confirmed
+
+### Authentication Flow
+
+1. User authenticates with primary credentials
+2. Push notification sent to enrolled device
+3. User sees transaction context
+4. User approves or denies
+5. Auth0 receives response
+6. Authentication completes
+
+### Push Notification Content
+
+Notification includes:
+- Application name
+- Transaction context
+- User location (if available)
+- Browser/device information
+- Approve/Deny options
+
+## One-Time Password (OTP)
+
+### When to Use OTP
+
+OTP serves as:
+- Fallback when push fails
+- Primary factor when configured
+- Offline authentication option
+
+### OTP Characteristics
+
+Code Format:
+- 6 digits
+- 30-second validity
+- Automatic regeneration
+
+Compatibility:
+- Standard TOTP algorithm
+- RFC 6238 compliant
+- Works offline
+
+### Enabling OTP
+
+1. Enable One-Time Password as MFA factor
+2. Users enroll via Guardian app
+3. OTP available alongside push notifications
+
+## Guardian SDK
+
+### Purpose
+
+Embed Guardian capabilities in custom branded applications instead of using Auth0 Guardian app.
+
+### Available SDKs
+
+iOS SDK:
+- Swift/Objective-C support
+- Full Guardian functionality
+- Custom UI implementation
+
+Android SDK:
+- Java/Kotlin support
+- Full Guardian functionality
+- Custom UI implementation
+
+### SDK Features
+
+Enrollment:
+- Programmatic QR code scanning
+- Manual enrollment entry
+- Custom enrollment UI
+
+Authentication:
+- Push notification handling
+- OTP generation
+- Custom approval UI
+
+Management:
+- Device management
+- Enrollment deletion
+- Token refresh
+
+## Configuration in Dashboard
+
+### Enable Guardian
+
+1. Navigate to Dashboard > Security > Multi-factor Auth
+2. Enable Push Notifications factor
+3. Configure notification service
+
+### Customize Guardian
+
+Application Appearance:
+- Set application name
+- Configure accent color
+- Upload custom icon
+
+Notification Settings:
+- Configure push service credentials
+- Set notification timeouts
+- Enable/disable features
+
+## Best Practices
+
+### Deployment
+
+Start with Auth0 Guardian App:
+- Fastest deployment
+- No development required
+- Automatic updates
+
+Consider Guardian SDK When:
+- Brand consistency critical
+- Custom UX requirements
+- Integration with existing app
+
+### User Enrollment
+
+Clear Instructions:
+- Provide visual enrollment guide
+- Support multiple languages
+- Include troubleshooting steps
+
+Multiple Device Support:
+- Allow enrollment of multiple devices
+- Provide device management
+- Handle device replacement
+
+### Fallback Options
+
+Always Configure Fallbacks:
+- OTP for offline scenarios
+- SMS for non-smartphone users
+- Recovery codes for emergencies
+
+### Security
+
+Enforce App Security:
+- Require PIN or biometric on app
+- Educate users on settings
+- Monitor enrollment patterns
+
+## Troubleshooting
+
+### Push Notifications Not Received
+
+Possible Causes:
+- Network connectivity issues
+- Notification permissions disabled
+- Incorrect push service configuration
+- Device in Do Not Disturb mode
+
+Solutions:
+- Verify network connection
+- Check notification permissions
+- Review push service configuration
+- Test with OTP fallback
+
+### Enrollment Failures
+
+Possible Causes:
+- QR code expired
+- Camera permission denied
+- Network timeout
+- Clock synchronization issues
+
+Solutions:
+- Generate new QR code
+- Grant camera permissions
+- Check network connectivity
+- Sync device time
+
+### OTP Not Working
+
+Possible Causes:
+- Device clock out of sync
+- Wrong account selected
+- Code expired during entry
+- Enrollment corrupted
+
+Solutions:
+- Sync device time automatically
+- Verify correct account
+- Enter code immediately after generation
+- Re-enroll if persistent
+
+## Metrics and Monitoring
+
+### Available Metrics
+
+Track in Auth0 Dashboard:
+- Push notification delivery rates
+- Approval/denial rates
+- OTP usage frequency
+- Enrollment counts
+
+### Log Events
+
+Guardian events logged:
+- Enrollment success/failure
+- Push sent/delivered
+- Authentication approve/deny
+- OTP verification attempts