Meridian Alpha

Regulatory Library

Regulations that apply to Meridian Alpha and the controls that meet them
As of 9 Oct 2026
India · Central · Cyber & Technology

SEBI · Cybersecurity and cyber resilience

SEBI Cybersecurity and Cyber Resilience Framework (CSCRF), 20 August 2024

Open in Studio
Legal entity
Meridian Alpha Pvt. Ltd.
Applicability
Not applicable to Meridian Alpha · scoped for Listed entity
Locations
Mumbai Head Office (Bandra Kurla Complex), Bengaluru Technology Centre
Reporting cycle
Half-yearly · compliance

Requirement coverage · compliance position: gaps to close

5
requirements
  • Covered 00%
  • Partially covered 5100%
  • Evidence unavailable 00%
Controls
12
4 failed testing
Evidence approved
39/54
current cycle
Open findings (gaps)
5
1 high
Open actions
5
0 overdue

Requirements and the controls that meet them

RefRequirementApplicabilityControl objectiveControlsCoverage
IdentifyAsset and access governanceNot applicableAccess is approved, reviewed and removed on exit or role changeACC-01ACC-02ACC-04JML-01JML-02Partially covered
ProtectPrivileged and network accessNot applicablePrivileged access is just-in-time and restrictedACC-03CHG-03Partially covered
DetectContinuous security monitoringNot applicableSecurity events are logged, retained and monitoredLOG-01LOG-02Partially covered
RespondIncident response and reportingNot applicableIncidents, including supplier incidents, are assessed and reportedVEN-03LOG-01Partially covered
ProtectThird-party riskNot applicableThird parties are assessed, contracted and monitoredVEN-01VEN-02VEN-03Partially covered

Controls and current position

ControlWhat it checksSystemsTestEvidenceOpen findings
ACC-01MFA and SSO enforced for workforce accessAmazon Web Services (ap-south-1), Microsoft Entra ID, GitHub Enterprise CloudPass6 / 60
ACC-02User access provisioning is approved before grantMicrosoft Entra ID, SAP S/4HANA, ServiceNow ITSMPass6 / 60
ACC-04Quarterly user access review of in-scope applicationsMicrosoft Entra ID, Salesforce (Sales + Financial Services Cloud), SAP S/4HANANot tested0 / 50
JML-01Leavers are de-provisioned within 24 hoursDarwinbox HRMS, Microsoft Entra ID, SAP S/4HANAPass6 / 60
JML-02Mover access is recertified on role changeDarwinbox HRMS, Microsoft Entra ID, SAP S/4HANAFail9 / 91
ACC-03Privileged access is just-in-time and reviewedAmazon Web Services (ap-south-1), Microsoft Entra ID, SAP S/4HANAFail3 / 71
CHG-03Developers have no standing production access; deployments via pipeline onlyAmazon Web Services (ap-south-1), GitHub Enterprise CloudPass2 / 30
LOG-01Security events are centrally logged and monitored 24x7Amazon Web Services (ap-south-1), Microsoft Entra ID, Meridian Customer PortalPass3 / 40
LOG-02Audit logs retained 180 days online and 5 years archived, tamper-protectedAmazon Web Services (ap-south-1), SAP S/4HANANot tested0 / 00
VEN-03Supplier security incidents are assessed for impact and trackedPayGate Payment Gateway, Meridian Customer PortalFail2 / 41
VEN-01Critical third parties are risk-assessed before onboarding and annuallyPayGate Payment Gateway, Salesforce (Sales + Financial Services Cloud)Fail2 / 31
VEN-02Provider contracts include data protection and RBI audit clausesSalesforce (Sales + Financial Services Cloud)Not tested0 / 11

Open actions

ActionIssueOwnerDueStatus
REM-F-SOC2-02Mover access not removed timely (deviation in CC6.2 testing)Neha Iyer31 Oct 2026Open
REM-F-ITGC-02Standing privileged access in production AWSRahul Nair16 Oct 2026In Progress
REM-F-RBI-03Payment provider incident — incomplete credential rotationDeepa Menon10 Oct 2026In Progress
REM-F-RBI-02Material outsourcing: lapsed assurance and overdue reassessment (Outsourcing of IT Services 2023 §6/§9)Sanjay Kulkarni20 Oct 2026Open
REM-F-ISO-02Supplier agreement lacks information security clauses (A.5.20)Sanjay Kulkarni31 Oct 2026In Progress

Regulatory reporting for management, audit and compliance review. Applicability is as assessed in Prismet. Statutory returns and regulator filings are not prepared or submitted from Prismet.