Architecture Guarantee

We Analyze Settings.
Not Students.

EduPulse 365 is architected on a "Zero Content Access" principle. We connect to your admin configuration layer, never your user data layer.

How PulseScan Connects

Many security tools ask for broad "Global Admin" access. We don't. PulseScan uses a least-privilege Service Principal that can only read Configuration APIs.

We SEE:

"Is External Sharing enabled?"
"Are Guest Users allowed?"
"Is Legacy Auth blocked?"

We DO NOT SEE:

Student emails or chats.
Files in OneDrive/SharePoint.
PII (Personally Identifiable Information).

/// CONNECTION_LOG_V5.0

>> Connecting to Entra ID Config... SUCCESS
>> Reading Intune Device Policy... SUCCESS
>> Accessing Student_Grades.xlsx... BLOCKED
>> Reading User_Chat_Logs... BLOCKED
EduPulse Principle 143: Configuration Data Only

Aligned with Education Standards

FERPA

We identify sharing settings that risk FERPA violations by exposing student records publicly.

CIPA

Ensuring your tenant's safety settings align with Children's Internet Protection Act requirements.

COPPA

Monitoring age-gating and data collection settings for students under 13.

NIST CSF

Our baseline mapping aligns with NIST Cybersecurity Framework best practices.

Technical FAQ

Do you store my data?

We store a snapshot of your configuration metadata (e.g., "MFA is set to Disabled") to generate your PulseScore. We do not store user-generated content.

Can EduPulse change my settings?

No. The PulseScan connection is Read-Only. We cannot accidentally break your environment. Remediation is performed by you (with our expert guidance) to ensure you maintain control.

How do we offboard?

Simply remove our Enterprise App registration from your Entra ID. Our access is instantly revoked. You remain in full control of the connection at all times.

Ready to validate your security posture?

Request a Security Review