Movahedi Solutions
Secure Software Development Lifecycle
1000823315 ONTARIO INC., operating as Movahedi Solutions, Mississauga, Ontario, Canada. Contact: mohammad@movahedi.ca. This page describes the development lifecycle for the public site, movahedi.ca, a static site. It does not describe a client system, which the company does not control, and it does not describe a software product lifecycle.
Source and deployment
The public site is built and deployed from GitHub, so the source for the live site is held in version control, and a change to the live site can be traced to its source. The site is delivered over HTTPS through Cloudflare. Detail: Infrastructure and Security Practices.
Gates before publish
- Copy checked. Site copy is checked for errors before publish. A file that fails the check is fixed before it ships.
- Links checked. Every internal link is checked against the built site before publish. A broken internal link blocks the publish, and the previous version keeps serving.
- Final-file check. Every file for an external submission is built as a clean final version, then checked for unfinished marks and blank signature blocks before it is shown or uploaded. The file that passes is the exact file that is uploaded.
- Header scan as a check. The third-party header scan, October 28, 2026 (see Security Practices for the result), is used as a dated check on the public site.
- SSL check as a check. SSL Labs returned grade A on all four endpoints tested, assessed October 28, 2026, at 01:00:26 UTC, at SSL Labs: movahedi.ca. Detail: DNS and SSL Checks. No A+ SSL grade is claimed, because the grade returned was A.
Detail on the full method: How work is planned, checked, and improved, October 28, 2026, including the Recorded process checks table and Preventing known publishing mistakes.
How this works
A site change is written, checked for errors and broken links, published, verified live, and recorded with a dated Updates line on the Trust Center hub. A submission file is built clean, checked mechanically, shown for approval, and only then uploaded as that exact clean file.
Related pages
Scope and limits, stated briefly
Where a matter is to be confirmed per engagement, it is stated as such, and it is confirmed in writing for that engagement before work starts. Contact: mohammad@movahedi.ca.