Network Security Policy

Scope and responsibility

The company owner is responsible for network access decisions for Linkhaus production services, development environments, data stores, and administrative connections. Linkhaus uses managed services including Google Cloud Run, Cloud Storage, Neon, and Vercel. Provider infrastructure protections and Linkhaus application configuration have separate responsibilities.

Segregation and access

Production and development access must be separated through environment-specific credentials and permissions. Production personal data must not be copied into development without an approved purpose and suitable safeguards. Only application endpoints intended for public use may permit anonymous access. Administrative interfaces, service-to-service calls, and data stores must require appropriate authentication and least-privilege access.

Private connectivity, ingress restrictions, and firewall or allowlist rules must be used where appropriate and supported. Changes to public exposure must be reviewed by the owner before release. Provider-managed isolation must not be represented as proof that the entire application uses a private network.

Monitoring and response

Relevant access, authentication, and service logs must be enabled and reviewed for unusual activity. Alerts or reported anomalies must be investigated and recorded. Threat detection, intrusion prevention, or equivalent managed protections must be evaluated for each service; the owner must record which protections are enabled and any gaps. Suspected compromise follows the Incident Response Policy.

Review and evidence

The owner must review network exposure at least annually and after material infrastructure changes. Evidence must include access rules, service configuration, relevant monitoring settings, findings, and corrective actions. This policy does not assert that a dedicated NIDS or HIPS is currently deployed.