● TRUST CENTER

Verifiable evidence.
Audited annually.

Security and compliance documentation for executives, insurance reviewers, legal teams, vendor-risk teams, and enterprise buyers. Public statements below; NDA-gated artefacts available on request within five business days.

SOC 2 Type II
ISO 27001 SoA
IS Policy
BCDR Plan
IR Playbook
Pentest Summary
Insurance
Sub-processors
NDA · Verified clients only

1. Security & Compliance Overview

EFROS operates as a cybersecurity-first managed service provider. Every engagement runs under documented controls aligned to recognised frameworks. Independent attestations and partner-tier letters are reviewed annually and provided under NDA to qualified prospects.

2. Certifications & Partner Evidence

EFROS holds certifications and partner statuses across the major technology vendors and frameworks our clients require. Each is independently verified annually. Documentation, audit attestations, and partner-tier letters are available under NDA for qualified clients and their reviewers.

  • ISO/IEC 27001:2022 — Information Security Management
  • SOC 2 Type II — Annual attestation
  • Microsoft Solutions Partner — verified via Microsoft Partner Center
  • AWS Advanced Tier Services Partner
  • Cisco Premier Partner
  • CompTIA Security+ — team-wide credentialing

3. Documentation Available Under NDA

The following are released to qualified clients and their insurance, legal, or audit reviewers under mutual non-disclosure agreement.

  • SOC 2 Type II Report (current period)
  • ISO 27001 Statement of Applicability (SoA)
  • Information Security Policy + supporting standards
  • Business Continuity & Disaster Recovery Plan
  • Incident Response Playbook (sanitised)
  • Third-party penetration test executive summary
  • Insurance certificates — cyber, professional indemnity, general liability
  • Sub-processor list with data flow diagram

4. Data Handling

Client data remains in the client's own tenant by default. EFROS engineers operate with the minimum-necessary access required for the engagement. Read-only auditor or global-reader roles are preferred where the task allows; elevated access is time-boxed, logged, and reviewed.

  • Default: data stays in client tenant; EFROS does not retain custody
  • Encryption at rest: AES-256 on all EFROS-managed systems
  • Encryption in transit: TLS 1.2+ with HSTS + MTA-STS enforcement
  • Audit logs: 12-month minimum retention; longer for regulated scope
  • Access reviews: quarterly for all client tenants
  • Sub-processor disclosure: complete list under NDA

5. Privacy & Confidentiality

EFROS operates against GDPR, UK GDPR, CCPA / CPRA, HIPAA (where BAA in place), and PIPEDA expectations. Every engagement contract includes confidentiality covenants. Employees are bound by individual confidentiality agreements and trained annually on data-handling procedures.

  • Annual data-protection training for every employee
  • Background screening for production access
  • Multi-factor authentication on every system
  • Privileged access management (PAM) with session recording for sensitive systems
  • Onboarding / offboarding within 4 business hours under documented runbook

6. Incident Response Process

If an incident affects a client environment, the 24×7 SOC contains first, communicates with the client's designated incident contact, and follows the runbook documented during the engagement onboarding.

  • Severity 1 (customer-impacting): 30-minute acknowledgement, 4-hour resolution target
  • Designated incident contact named at engagement start, validated quarterly
  • Forensic readiness: timeline preservation, memory captures, chain-of-custody
  • Regulatory notification timing tracked against jurisdiction (e.g. OCR for HIPAA, NYDFS 23 NYCRR 500 §500.17, GDPR 72-hour clock)
  • Post-incident review with root-cause analysis and remediation roadmap

7. Insurance & Risk Documentation

EFROS carries cyber-liability, professional-indemnity, and commercial-general-liability coverage. Certificates of insurance are provided to qualified prospects under NDA. Carrier-specific attestations available for clients whose own cyber insurance requires vendor-side documentation (Beazley, Chubb, AIG, Travelers, and the major specialty markets).

8. Vendor Due Diligence Contact

For procurement reviewers, security questionnaires (SIG, CAIQ, SAQ, custom), and audit requests, route directly to our compliance team. We typically return completed questionnaires within five business days.

  • Email: trust@efros.com
  • Standardised: SIG Core, SIG Lite, CSA CAIQ
  • Custom questionnaires: returned with evidence references and policy excerpts
  • Audit calls: scheduled within 10 business days, attended by EFROS security lead

9. Responsible Disclosure

Security researchers reporting vulnerabilities in EFROS-operated systems or client environments under our scope are welcomed. We follow a coordinated disclosure model and do not pursue legal action against researchers who act in good faith.

  • Contact: security@efros.com
  • PGP key + security.txt published at /.well-known/security.txt
  • Triage: acknowledged within 2 business days
  • Validation window: typically 7-30 days depending on scope
  • Coordinated disclosure window: 90 days by default, adjustable for active exploitation
10. Frequently Asked

Questions executives ask.

How do I verify EFROS's partner statuses?

Microsoft Solutions Partner status is verifiable via Microsoft Partner Center. AWS Partner status is verifiable via the AWS Partner Network directory. Cisco Premier status via the Cisco Partner Locator. ISO 27001 and SOC 2 attestations are released under NDA.

Will EFROS sign our security questionnaire?

Yes. Standardised questionnaires (SIG, CAIQ) are returned within 5 business days. Custom questionnaires within 10 business days. We sign with evidence references, not with claims that exceed our actual controls.

Will EFROS sign a Business Associate Agreement (BAA)?

Yes. We sign BAAs with every healthcare client and operate HIPAA-aligned controls as a default. The BAA is signed before any PHI-relevant systems are touched.

Where does our data live?

In your tenant. EFROS engineers operate against your Microsoft 365, Google Workspace, AWS, Azure, or Google Cloud tenant under read-only or scoped credentials. EFROS does not retain custody of client data outside the agreed retention window for evidence (typically 12 months) and destruction is verifiable.

What happens at the end of an engagement?

All documentation, configuration, and runbooks remain in your tenant. EFROS retains evidence files under encryption for the contractually agreed retention period (default 12 months), then destroys them with verifiable sign-off. You can request earlier destruction at any time.

How are background checks handled?

Every EFROS employee with production access undergoes a criminal background screening through a reputable vendor before starting. Renewed for sensitive engagements. References available under NDA.

● Visible proof

What the deliverable actually looks like.

Anonymized samples drawn from real engagements. Every artifact below is a representation of what an EFROS client receives as part of an assessment, incident-response retainer, or managed service. Not marketing slides — operational outputs.

EFROS Passive Assessment · Sample · Anonymized
Overall security score
86Grade Bout of 100
Posture
Above-average for industry · 3 priority remediations
DomainA
DNSSEC · CAA89/100
Email AuthB
SPF · DKIM · DMARC72/100
Web SecurityA
HSTS · CSP91/100
BrandA+
Typosquats · BIMI96/100
InfrastructureA+
DNSBL · CDN100/100
ComplianceC
GDPR · security.txt65/100
P2
F-007 · MediumCVSS 6.1 · Confirmed
DMARC policy at p=none allows spoofed mail through

Recommended: move to p=quarantine within 14 days after a 30-day aggregate-report review, then to p=reject. Owner: IT lead. Effort: 2 hours.

Page 3 · 14CONFIDENTIAL · SAMPLE · COPY-A1F2B3
Incident Response · Ransomware · Sample · Anonymized
3 min
Time to triage
15 min
Time to client notify
10 hr
Time to restore
  1. T+0Detection· SOC analyst · automated
    EDR isolates first compromised endpoint

    Defender for Endpoint blocks file-encryption pattern, isolates host from network. Initial alert fires in SOC console.

  2. T+3 minDetection· SOC tier-2
    SOC analyst opens incident, runs scope query

    Identity, lateral-movement, and persistence indicators pulled from SIEM. Two additional endpoints flagged with matching IOCs.

  3. T+8 minContainment· SOC tier-2 · IR lead
    Containment: identity + endpoint quarantine

    Compromised user revoked, sign-in sessions terminated. All three endpoints isolated. Lateral targets pre-emptively isolated.

  4. T+15 minContainment· IR lead → Client CISO / Owner
    Client notification + IR call bridge opened

    Notification per pre-agreed SLA. Bridge opened with client lead, EFROS IR lead, and SOC on the line. Initial scope and impact statement delivered.

  5. T+45 minInvestigation· DFIR engineer
    Forensic acquisition + threat-actor identification

    Memory image, disk snapshot, and log preservation. TTPs matched against known affiliate. Initial-access vector identified (phished M365 account, no MFA).

  6. T+4 hrRecovery· Senior engineer + DFIR
    Eradication + clean-rebuild starts on isolated VLAN

    Confirmed-clean baseline images deployed to a quarantine VLAN. Patient zero credential rotated, app-password reset across affected services.

  7. T+10 hrRecovery· Backup engineer
    Restore from immutable backup, verified clean

    Three-2-1 backup restored to clean infrastructure. Hash integrity verified, AV scan clean. User-facing systems back online on a watched VLAN.

  8. T+48 hrReview· IR lead + Client
    Post-incident review + hardening plan

    Written report delivered: TTPs, IOCs, what worked, what didn't, mandatory hardening (MFA, Conditional Access, log retention). Lessons documented for tabletop.

Real-world sequence from a logistics-sector engagement. Customer details anonymized. EFROS retainer clients receive a written post-incident report with TTPs, IOCs, and a mandatory hardening roadmap within 72 hours of resolution.
Microsoft 365 Hardening · Sample · Anonymized
6
Implemented
4
Partial
5
Missing
Identity· Implemented
MFA enforced for all licensed users

Conditional Access policy 'Require MFA for all users' active

~
Identity· Partial
Privileged accounts on FIDO2 or Authenticator with number-match

3 of 5 Global Admins still on SMS — schedule cutover

Identity· Implemented
Conditional Access blocks legacy authentication

Policy active; 0 legacy-auth sign-ins last 30 days

Identity· Missing
Risk-based sign-in policy and user-risk policy enabled

Entra ID P2 features available but not configured

~
Email security· Partial
SPF / DKIM / DMARC at p=reject with aggregate reporting

DMARC at p=quarantine; ready to move to p=reject in 30 days

Email security· Implemented
Anti-phishing impersonation protection (Defender for Office 365)

Mailbox-intelligence on; 4 executives in protected-users list

Email security· Implemented
Safe Links and Safe Attachments policies tuned

Dynamic delivery on; click-time URL rewriting active

Email security· Missing
External-sender warning banner on inbound mail

Transport rule not deployed — recommended for BEC defense

Endpoint· Implemented
Defender for Endpoint or third-party EDR on all devices

Defender P2; 248 of 248 devices reporting

~
Endpoint· Partial
Intune compliance policy gates Conditional Access

Windows compliant; macOS and iOS compliance policies pending

Endpoint· Missing
Attack Surface Reduction rules in audit-then-block mode

ASR rules not enabled — high-leverage hardening

Data· Missing
Sensitivity labels with auto-classification on top 3 categories

Purview unlicensed or unconfigured

~
Data· Partial
DLP policies for credit-card / SSN / health data

DLP on email only — extend to Teams, SharePoint, OneDrive

Audit· Implemented
Unified audit log enabled and retention extended to 1 year+

Audit log on; retention at default 180 days — extend to 365

Audit· Missing
Alert policies routed to SOC or 24×7 monitoring

Alerts firing into a shared inbox no one watches at 2 AM

Sample shown. The full M365 posture assessment covers 60+ controls across Identity, Email, Endpoint, Data, Apps, and Audit. Evidence is collected directly from your tenant under a read-only delegated app permission.
Backup & DR Readiness · 3-2-1-1-0 · Sample · Anonymized
6
Pass
2
Warn
2
Fail
  • 3 copies of every protected workload· Pass

    Production + on-prem repo + cloud repo for tier-1 systems

    Evidence: Veeam job report: 100% of tier-1 systems with 3 copies

  • 2 different storage media· Pass

    Disk-based repo + object-storage cloud tier

    Evidence: Wasabi S3 immutable tier + local ReFS volume

  • 1 copy off-site, geographically separated· Pass

    Cloud copy in a region >300 km from primary site

    Evidence: Cloud copy in EU-Central, primary in EU-West

  • !
    1 copy immutable (object-lock or air-gap)· Warn

    Hardened repository or S3 Object Lock with retention period

    Evidence: Object Lock at 14 days — recommended minimum is 30 days

  • 0 backup verification errors· Fail

    SureBackup or recovery-verification job passes on every restore point

    Evidence: 4 of 12 tier-1 jobs without verification configured

  • !
    Quarterly full-restore test, written record· Warn

    A complete restore-to-clean-infrastructure dry-run with documented timing

    Evidence: Last test 11 months ago — overdue per policy

  • RTO target documented per workload tier· Pass

    Recovery Time Objective per system, agreed with the business

    Evidence: Tier-1: 4 hr · Tier-2: 24 hr · Tier-3: 72 hr (signed off)

  • RPO target documented per workload tier· Pass

    Recovery Point Objective expressed in minutes/hours of data loss

    Evidence: Tier-1: 15 min · Tier-2: 4 hr · Tier-3: 24 hr

  • Backup credentials separated from production AD· Fail

    A compromised domain admin must not be able to delete backups

    Evidence: Veeam service account is a domain admin — high-risk finding

  • Backup repository monitored by SOC· Pass

    Alerts route to a 24×7 watched queue, not a shared inbox

    Evidence: Veeam ONE → Wazuh → SOC ticketing pipeline live

Modeled on Veeam's 3-2-1-1-0 rule. The full backup-readiness assessment includes a live quarterly restore-test exercise, RTO/RPO validation per workload, and immutable-repo configuration review.

Request documentation.

For vendor-risk reviewers, audit teams, or enterprise procurement. We typically return completed questionnaires within 5 business days.