A framework for appropriate use, accountable ownership, technical assurance, privacy, retention and ongoing oversight.
Before you use MachForm
MachForm is an online service for creating fillable forms and managing submitted information. It is appropriate for routine applications, registrations, requests and simple surveys when the information collected is necessary, proportionate and protected.
Core rule
Use MachForm only for the minimum information necessary for the stated University purpose. Routine personal information may be collected where appropriate. Sensitive, confidential, regulated or high-risk information requires additional review and may require a different institutional platform.
What information may be collected?
Classify the information you plan to collect using York's Information Security Classification Standard and follow its handling requirements. Assess the information in context. Several routine fields combined together, a large number of records, or information whose disclosure could cause significant harm may create a higher-risk collection even when no individual field appears sensitive.
Generally permitted
Routine personal information needed for an ordinary University activity:
- Name and York email address
- Telephone number or mailing address where necessary
- Faculty, department, affiliation or role
- Basic registration or event preferences
Data minimization, access and retention requirements still apply.
Review required
Consult Privacy and Information Security before collecting:
- Student or employee numbers
- Date of birth or demographic information
- Accommodation-related or detailed employment information
- Personal-information file uploads
- Large datasets or combinations that increase potential harm
Do not collect without explicit approval
- SIN, passport, driver's licence or health card numbers
- Banking, payment or credit-card information
- Passwords or authentication secrets
- Detailed medical, disciplinary, legal or financial records
- Other Restricted or high-risk information
Payments
MachForm must not process payments or collect payment-card information. Contact York's Finance Division for an approved payment solution.
Requirements for every form
- Collect only information demonstrably necessary for the stated purpose.
- Use a clear notice explaining purpose, authority, intended use, access and contact information.
- Limit form and submission access to authorized people with a business need.
- Do not include sensitive submission data or attachments in email notifications.
- Set a retention period in accordance with York's Common Records Schedule (CRS), and securely delete or transfer information when it is no longer required in MachForm.
- Reassess the form before materially changing its purpose, audience, data fields, integrations or file uploads.
Governance and accountability
Every MachForm site must have a named accountable owner. Without one, the MachForm site will not be enabled.
| Role | Accountability |
|---|---|
| MachForm Site Owner | Confirms the purpose, authority, necessity of each data element, intended users, retention period and continuing business need. Supervises the builds and manages forms within the approved configuration; applies least privilege; does not add administrators or alter security controls outside the managed process. |
| Platform owner | Maintains the approved platform, configuration, patching, backup, logging, vulnerability management and business continuity arrangements. |
| Privacy and Information Security | Review higher-risk collections, define required safeguards, assess exceptions and determine whether another platform is required. |
Technical assurance and monitoring
The Platform owner is responsible for the following technical assurances:
- Review privileged access and administrator assignments regularly.
- Run only supported, York-approved MachForm, operating-system, database, web-server, PHP and CMS versions.
- Use Passport York SSO; disable local administrative authentication unless an exception is formally approved.
- Keep application data and uploads outside the web root and prohibit direct public retrieval.
- Maintain York-approved application hardening, browser-security instructions and Apache security headers.
- Perform scheduled OWASP-aligned application testing and vulnerability scanning, including enumeration, object-level authorization, authentication/session handling and bulk-access scenarios.
- Resolve or formally accept Critical and High findings before service release; track lower findings to closure based on risk.
- Centralize application, web, proxy and web-application-firewall telemetry where available, and monitor abnormal request patterns, enumeration and unusual bulk access.
Exceptions, incidents and support
Exceptions
An exception requires a documented business rationale, defined scope and duration, Privacy and Information Security assessment, compensating controls, accountable approval and an expiry/review date. Operational convenience alone is not sufficient.
Suspected exposure or misuse
Stop the collection where safe to do so, preserve relevant evidence and report the issue immediately through York's established Information Security and privacy-incident processes. Do not investigate by downloading or circulating additional personal information.
Access and support
Contact askit@yorku.ca for access, service support, platform selection or review routing. Administrators must not independently create new installations or bypass managed controls.
York University Information Security
For help, contact askit@yorku.ca.
