Security overview
This overview describes the public courseorbit.com website. Course delivery environments require a separate, configuration-specific review.
Public-site boundary
- The public document root contains one PHP front controller and intentionally public CSS, JavaScript, and image assets.
- Templates, YAML and Markdown sources, handlers, logs, lead records, and configuration remain outside the document root.
- The public site has no login, database, shopping cart, or student course activity.
- Forms validate inputs server-side, use same-origin checks, honeypots, request-size limits, and rate limits.
Browser and server controls
The web server is configured for HTTPS transport protection, a restrictive Content Security Policy, frame blocking, MIME-type protection, limited browser permissions, no directory listing, and no server signature. Operational deployment must verify that these headers are active at the hosting edge.
Stored public-site information
Instructor and institutional review requests are stored outside the web root and routed to the assigned team. First-party analytics store aggregate daily counts only. They do not retain IP addresses, user agents, form values, full referrer addresses, or persistent visitor IDs.
Responsibility boundaries
This page makes no blanket security, compliance, or uptime guarantee. Course Orbit is responsible for the systems it operates; the institution for its credentials, sign-on, and network controls; and the LMS provider for the security and availability of the LMS. See the responsibility matrix.
Incident reporting
Report a suspected security or privacy incident through the Support Center or privacy@courseorbit.com. Include the affected system, date and time, and a description; do not email passwords or sensitive student records.