Customer records sit behind every support and administrator login
Telecom providers, VoIP firms, and resellers give staff and partners access to customer records. Start with the accounts you can control.
Or email hello@teclara.tech
Short on time? Let your favourite AI sum up Teclara.
Where the risk shows up
Access to customer information changes hands constantly.
Support teams turn over, partners resell service, and administrators hold keys to more than one system. The exposure sits in the accounts and devices around the service, which is where this program works.
New support staff
Agents need customer context on day one
Support roles are often hired in groups and need customer files and conversations immediately. Named accounts with role-based access make the next removal as fast as this grant.
Partners and resellers
Someone outside the company needs access
Channel partners and contractors often get shared folders or guest accounts. Guest access is reviewed on a schedule instead of left to accumulate.
Account changes
A caller asks to change a customer account
Social engineering aimed at support staff is how SIM swap and porting fraud often begins. Awareness training covers the pattern, and the verification steps stay in your support process.
After an incident
Someone asks what was reached
An investigation needs sign-in history, mailbox activity, and file access records that were being kept before anything happened.
What we run
A support account can reach more than one customer
The first review maps who has privileged access, where customer information lives, and which systems are inside the managed security program. That map sets the response and recovery boundaries before an incident.
Identity
Limit administrator access
Protect Microsoft 365 or Google Workspace administrator accounts with multi-factor authentication, role limits, and sign-in monitoring. Access to separate provisioning and network consoles is assessed only when those systems are placed in scope.
Customers
Control access to customer records
Review who can reach customer files, support conversations, and shared documents in the cloud tenant. Billing, ticketing, and subscriber databases need their own access and retention decisions.
Support
Remove access when roles change
Staff, contractors, and partners receive named access where the platform supports it. Offboarding removes accounts, sessions, and shared access from the managed environment through a documented process.
Devices
Protect supported staff devices
Supported laptops and phones placed in the program receive managed endpoint protection, encryption, and security updates. Alerts follow the agreed investigation and escalation process.
Email
Reduce account and domain impersonation
Email filtering, sign-in controls, and domain authentication help protect customer communications and internal requests. Changes to sensitive customer or payment details still need an independent verification process.
Recovery
Test recovery for cloud data
Microsoft 365 or Google Workspace data in scope is backed up independently and tested for recovery. Subscriber, billing, provisioning, voice, and network systems need separate recovery plans.
Who asks for proof
Privacy law, business customers, and insurers each ask for records.
Telecom providers under federal jurisdiction are covered by PIPEDA for customer and employee information, which adds a specific record-keeping duty to the usual questionnaires.
- Office of the Privacy Commissioner
- Can you produce your record of every breach of security safeguards from the last 24 months?
- Alert, investigation, and response history for the systems in scope, which feeds the breach record PIPEDA requires you to keep. The decision to report stays with you.
- Business customers
- Who at your company can see our account information, and how is that access controlled?
- The access model for customer folders and shared mailboxes, MFA coverage, and offboarding records for staff and partners.
- Cyber insurer, at renewal
- Is MFA enforced for administrators and support staff? Are backups tested?
- MFA and administrator role reports, device coverage, and the backup scope with the last restore test.
What stays yours
The provider decides which customer information rules, contracts, regulatory duties, and notification requirements apply to its services. Teclara operates and documents the security controls agreed in scope. Network and service infrastructure, specialist platforms, and regulatory interpretation require separate owners and written scope.
The program underneath
The same managed program runs under every industry.
Managed Security & Compliance is one service. What changes for your provider is the access model, the evidence, and the calendar it is run around.
- Human-led monitoring
- A 24/7 security team detects and responds to threats, not just an automated alert.
- Endpoint protection
- Managed detection and response on supported staff devices placed in scope.
- Email and fraud protection
- Controls for phishing, impersonation, and invoice fraud, with suspicious activity reviewed.
- Cloud backup and recovery
- Daily backup for the Microsoft 365 and Google Workspace platforms you use, including both when you use both, with tested restores.
- Login monitoring
- Cloud sign-ins watched for account takeover, with response following an agreed process.
- Patching and vulnerability management
- Systems patched on a defined schedule, with known weaknesses prioritized by risk.
- Security awareness training
- Ongoing training and simulated phishing to keep the team sharp.
- Tenant configuration
- Microsoft 365 or Google Workspace settings reviewed and updated against the security baseline.
On Microsoft 365
- MFA, Conditional Access, and administrator role review
- SharePoint, OneDrive, and support mailbox access controls
- Managed endpoint protection on supported staff devices
- Sign-in and sharing records retained for review
On Google Workspace
- MFA and administrator access controls
- Gmail phishing and impersonation protection
- Shared-drive and external-sharing reviews
- Admin and sign-in records retained for review
Configuration updates are part of the service. When our security baseline changes, your environment is updated without a separate project fee.
Managed security scope
- Staff identities, email, files, and sharing in Microsoft 365 or Google Workspace.
- Supported staff devices, cloud backup, monitoring, and written control records.
Scope to agree separately
- Billing, ticketing, subscriber, and provisioning platforms, including their administrator access and recovery.
- Carrier core, routing, switching, voice, radio, and field infrastructure.
Frequently asked questions.
Can Teclara secure our carrier network?
The managed program starts with Microsoft 365 or Google Workspace, supported staff devices, email, cloud backup, and the controls agreed in scope. Routing, switching, voice, radio, and other carrier infrastructure require a separate assessment, owner, and written scope. We will identify those boundaries during the risk review.
What about billing and provisioning systems?
We map who administers those systems and how staff sign in during discovery. Changes, monitoring, backup, and response inside each billing or provisioning platform are included only if its access, technical requirements, and responsibilities are agreed separately.
How do you protect customer information?
We review access to customer files, support mailboxes, and shared documents in the managed cloud tenant. Sign-in controls, staff-device protection, offboarding, and backup can then be applied to the systems in scope. Subscriber databases and ticketing platforms need their own controls and owners.
Can you provide evidence for customer or insurance reviews?
Yes. Reporting can document the controls Teclara operates, including administrator access, sign-in policies, supported-device coverage, backup and restore tests, and alert handling. The provider remains responsible for its answers, contracts, insurance application, and regulatory conclusions.
What happens when a security alert fires after hours?
The security team reviews alerts and follows the agreed response and escalation process around the clock. Available containment actions depend on the systems, access, and authority placed in scope. The provider keeps responsibility for service continuity and any required customer or regulator notifications.
Short on time? Let your favourite AI sum up Teclara.
Review who can reach customer records and service tools
We review sign-ins, administrator roles, staff devices, email, sharing, and cloud backup in your Microsoft 365 or Google Workspace environment. We document where billing, provisioning, and network systems need separate owners or a separate scope.