Security & Authentication Mechanisms

Relevant source files

The following files were used as context for generating this wiki page:

• sunrise-backend/create_admin.py
• sunrise-backend/config/settings.py
• .jules/sentinel.md
• task.md
• implementation_plan.md
• sunrise-angular/src/app/core/services/seo.service.ts

Sunrise Communication implements a multi-layered security and authentication strategy to protect administrative interfaces, manage system access, and ensure search engine visibility controls. The architecture spans both the Django-based backend for administrative control and the Angular-based frontend for secure lead discovery and search engine optimization.

Primary security components include environment-based configuration management, Django administrative authentication, and automated bot management via discovery layer protocols. The system prioritizes secure data handling for B2B/B2C lead generation without exposing sensitive e-commerce transaction logic.

Sources: implementation_plan.md, task.md

Administrative Authentication & Authorization

The project utilizes the Django authentication framework to secure the backend management interface. Access to the product catalog, service data, and administrative tools requires valid credentials.

Administrative User Provisioning

A dedicated utility script, create_admin.py, manages the creation of administrative superusers. This script checks for the existence of a user before attempting creation to prevent duplication errors.

# sunrise-backend/create_admin.py:8-14
if not User.objects.filter(username=username).exists():
    User.objects.create_superuser(username=username, email=email, password=password)
    print(f"Superuser '{username}' created successfully.")
else:
    print(f"Superuser '{username}' already exists.")

Sources: sunrise-backend/create_admin.py:8-14

Backend Security Configuration

The Django backend configuration in settings.py defines the security parameters for the application. Key settings include:

• Secret Key Management: Uses a unique secret key for cryptographic signing.
• Debug Mode: Controls the verbosity of error messages.
• Allowed Hosts: Restricts the hostnames the application can serve.

Setting	Purpose	Configuration File
SECRET_KEY	Cryptographic signing for sessions and tokens	config/settings.py
DEBUG	Toggles detailed error reporting	config/settings.py
ALLOWED_HOSTS	Defines valid host headers	config/settings.py
INSTALLED_APPS	Includes django.contrib.auth for security	config/settings.py

Sources: sunrise-backend/config/settings.py

Agentic & Bot Discovery Security

The system implements a discovery layer that controls how AI agents and search engine crawlers interact with the application. This prevents unauthorized scraping while enabling high-intent discovery.

Bot Management via Robots.txt

The public/robots.txt file explicitly permits or restricts access to various user-agents. It includes specific permissions for AI-based agents such as GPTBot, ClaudeBot, and Google-Extended to facilitate machine-to-machine discovery.

The diagram shows the filtering logic for incoming bot requests based on the robots.txt configuration.
Sources: task.md, sunrise-angular/public/robots.txt

Machine-Readable Security Manifests

The project deploys structured manifests to provide authoritative technical specifications to machine agents:

• llms.txt: Standard manifest for AI discovery.
• llms-full.txt: In-depth technical specifications and SLAs.
• llms.json: Structured OpenAPI manifest for programmatic discovery.

Sources: task.md, implementation_plan.md

Frontend Security & Data Integrity

The Angular frontend utilizes specific architectural patterns to maintain data integrity and secure communication with the backend.

Signal-Based State Management

The application uses Angular Signals to manage state reactively and securely. This approach ensures that data changes are tracked efficiently and prevents unauthorized direct modification of private state within services like ProductService.

The diagram illustrates the encapsulation of state using read-only signals to prevent external mutation of data.
Sources: implementation_plan.md

SEO & Schema Security

The SeoService manages the injection of structured JSON-LD data. This metadata is generated server-side to ensure search engine crawlers receive consistent and secure information about entities such as LocalBusiness, Product, and Service.

Key Schema Nodes:

• @graph unified JSON-LD for route-level data.
• GeoCoordinates for localized trust and verification.
• AggregateRating to showcase verified social proof.

Sources: sunrise-angular/src/app/core/services/seo.service.ts, task.md

Summary of Security Components

Component	Function	File Path
Admin Provisioning	Automates superuser creation for backend access	sunrise-backend/create_admin.py
Django Auth	Core authentication and permission framework	sunrise-backend/config/settings.py
Discovery Layer	Controls AI and Bot access permissions	sunrise-angular/public/robots.txt
Signal Encapsulation	Protects frontend state from external mutation	implementation_plan.md
JSON-LD Injection	Ensures integrity of machine-readable metadata	sunrise-angular/src/app/core/services/seo.service.ts

Sunrise Communication effectively balances open discoverability for AI agents with strict administrative controls for backend operations, ensuring that lead generation data remains accurate and secure across the MMR (Mumbai Metropolitan Region) service corridor.

Sources: implementation_plan.md, task.md, sunrise-backend/config/settings.py