How to Choose Secure School Software
A guide to evaluating the security and suitability of school management software before trusting it with student data. Includes questions to ask and red flags to watch for.
Why Choosing the Right School Software Matters
Selecting school management software is one of the most consequential technology decisions a Philippine school can make. It affects every department — from admissions and registrar to finance, academics, and parent communication. When you adopt a school management system, LMS, or any EdTech tool, you're trusting that vendor with your students' most sensitive data.
The Online Learning Platform breach showed what happens when vendors don't take security seriously — 45,000 student records exposed. But security is just one dimension. A poor choice can also lead to workarounds, duplicate data entry, and even mid-year system switches that disrupt the entire school.
10 Critical Questions to Ask Every School Software Vendor
1. Does It Replace or Just Add to Our Existing Tools?
Good answers: "Our system replaces your separate enrollment, grading, billing, and communication tools with one integrated platform"
Red flags: The vendor talks about "integrating" with your existing tools rather than replacing them, or requires manual data transfers between modules
2. Is It Built for Philippine Schools?
Good answers: Support for DepEd compliance requirements, local payment methods (GCash, Maya), and Philippine-specific payroll calculations (SSS, PhilHealth, Pag-IBIG, BIR)
Red flags: The vendor claims "international standards" without demonstrating Philippine-specific features, or requires extensive customization for basic local requirements
3. Where Is Our Data Stored and Is It Encrypted?
Good answers: "In ISO 27001 certified data centers," "AES-256 encryption at rest, TLS 1.2+ in transit," with specific region controls (AWS/GCP/Azure)
Red flags: "We're not sure," storage on office servers, or "We use HTTPS" as the only security measure
4. Who Has Access to Our School's Data?
Good answers: "Only authorized support staff with audited access," "Role-based access controls with comprehensive audit logging"
Red flags: "Our developers can see everything," "All our staff have access," or vague claims of "industry-standard security"
5. Is Our Data Isolated from Other Schools?
Good answers: "Logical or physical data isolation per school," "Separate databases per client"
Red flags: "All schools share one database" (co-mingled data)
6. What Is the True Total Cost?
Good answers: Transparent per-student pricing with all fees disclosed upfront — implementation, training, support tiers, and renewal pricing
Red flags: Hidden implementation fees, tiered support charges not mentioned in initial pricing, or unclear renewal price increases
7. How Do You Handle Security Incidents?
Good answers: "We have a documented incident response plan and will notify you within 24 hours," with clear escalation procedures
Red flags: "That hasn't happened to us" (everyone is a target), or no documented incident response plan
8. Are You Compliant with the Data Privacy Act and Registered with the NPC?
Good answers: "Yes, here's our NPC registration number," with a standard Data Processing Agreement readily available
Red flags: Unfamiliarity with the NPC or the Data Privacy Act, reluctance to sign a DPA
9. What Happens to Our Data If We Stop Using Your Service?
Good answers: "You own your data — you can export everything in standard formats anytime, and we delete it within 30 days of contract end"
Red flags: Permanent data retention, no export options, or data held hostage
10. What Does Your Support and Implementation Look Like?
Good answers: Local support staff who understand Philippine school contexts, assistance with data migration, comprehensive training for all user types, and post-implementation support through critical periods (enrollment, grading)
Red flags: Distant help desks with no Philippine school experience, self-service-only onboarding, or no migration assistance
Red Flags to Watch For
- No privacy policy on their website
- Unable to explain their security practices clearly
- Resistance to signing a Data Processing Agreement
- No mention of Data Privacy Act or NPC compliance
- Free platforms that monetize through student data
- No clear data retention or deletion policies
- Using outdated technology (Flash, HTTP-only, etc.)
- No two-factor authentication option
- Admin-only demos that don't show teacher, parent, or staff views
- No mobile-first design (critical for Filipino parents and teachers)
- No support for DepEd requirements or local payment methods
Building an Evaluation Scorecard
When comparing vendors, create a weighted scoring system:
- 3 = Excellent — Fully meets or exceeds the requirement
- 2 = Adequate — Meets the requirement with minor gaps
- 1 = Concerning — Partially meets the requirement
- 0 = Unacceptable — Does not meet the requirement
Rate each vendor across all 10 questions above and request references from schools of comparable size and type. Weight security and data privacy questions more heavily — a great feature set means nothing if student data is compromised.
Choosing With Confidence
The right school software vendor should be transparent about both their security practices and their understanding of Philippine school operations. They should be willing to put commitments in writing, demonstrate the system from every user's perspective, and provide local support when you need it. If a vendor can't answer these questions clearly, consider that a red flag — your students' data and your school's operations deserve better.