Rule · SECP · 12 Aug 2025
The Securities and Exchange Commission of Pakistan mandates pre-qualification requirements for Digital Asset Management Companies and other Asset Management Companies utilizing digital platforms to obtain No Objection Certificates from trustees. These requirements enforce strict cybersecurity controls, including secure access management, network perimeter protection, data encryption, and incident response protocols, alongside mandatory cybercrime insurance. Specific obligations for smartphone applications include multi-factor authentication, session timeouts not exceeding thirty minutes, PII storage within Pakistan, and adherence to detailed mobile app security standards in Annexure A.
No. SCD/PRDD/CIRCULAR/74/2025
August 01, 2025
The Securities and Exchange Commission of Pakistan (the “Commission”) in exercise of its powers conferred under Section 282B(3) of the Companies Ordinance, 1984 (XLVII of 1984) read with provisions of Regulation 67AL(a)(ii) of the Non-Banking Finance Companies and Notified Entities Regulations, 2008 (the “NBFC Regulations”) hereby specifies the following pre-qualification requirements for Digital Asset Management Company (Digital AMC) for seeking NOC from respective trustees.
These requirements are applicable to Digital AMCs as well as the AMCs which are utilizing Digital Platforms for provision of services to their investors/unitholders.
The Digital AMC shall adhere to the following requirements for provision of Digital Asset Management Services through digital platforms:
a. Open Web Application Security Project (OWASP) Mobile Application Security Verification Standard;
b. OWASP Mobile Application Security Testing Guide; and
c. OWASP Web Application Security Testing.
a. Secure Access Management infrastructure ensuring:
NIC Building, 63 Jinnah Avenue, Blue Area, Islamabad.
Tel: 051-9207091-4, Fax. No. 051-9100473
```
```markdown
SECURITIES AND EXCHANGE COMMISSION OF PAKISTAN SPECIALIZED COMPANIES DIVISION FUND MANAGEMENT DEPARTMENT
i. Logging and backups:
2.3. The Digital AMC shall avail cybercrime insurance policy to indemnify losses that may arise due to cyber-attack/cybercrime on their digital platforms.
2.4. The Digital AMCs shall ensure compliance with the additional requirements relating to the Smartphone Application, as provided in Annexure – A to this Circular.
2.5. In case of a smart phone application, the Digital AMC at the time of launching of app shall provide license status along with NOC granted by the Trustees for respective App to Google Play Store and/or App Store. Proof for the same shall subsequently be provided to the Commission and maintained by the Digital AMC as record. The app on Google Play Store/App Store (Apple Inc.) shall only be hosted with the URL which is provided on SECP Approved Digital Platform List.
2.6. Data related to Personal Identifiable Information (PII) shall not be stored on any cloud infrastructure outside the jurisdiction of Pakistan.
Explanation: PII means any information relating to an identified or identifiable natural person who can be identified, directly or indirectly, in particular by reference to an identifier.
However, the global cloud infrastructure resources and computing services may be utilized, including but not limited to networks, servers, applications, and services such as on-demand self-service, broad network access, and resource pooling.
Furthermore, when utilizing software application services through global cloud infrastructure, Digital AMCs shall ensure the encryption or anonymization of customers' PII, preventing their identities from being readily inferred.
For purposes of clarification, the Digital AMCs shall store sensitive PII within Pakistan with one cloud provider, while it may employ another local or foreign cloud provider for specific software application services. These services may include, but are not limited to, Infrastructure as a Service
NIC Building, 63 Jinnah Avenue, Blue Area, Islamabad.
Tel: 051-9207091-4, Fax. No. 051-9100473
```
```markdown
[See Clause 2.4]
Note: The term "Company" is used as replacement for "Digital Asset Management Company".
App Requirements – covers the entire mobile app ecosystem involved in capturing, storing, processing and transmitting financial/non-financial information. The Companies are responsible to ensure that their mobile apps and associated infrastructure is aligned with these requirements. The Company may develop mobile apps in-house, through outsourcing or by a combined approach. To manage mobile app development projects, Company shall:
(i) Put in place necessary app documentation including manuals on development, testing, trainings, production, operational administration, user guides and Service Level Agreements (SLAs);
(ii) Carry out vulnerability assessment, penetration testing and performance assessment of mobile apps to ensure effective and smooth operation before deploying the same in production environment;
(iii) Carry out system and user Acceptance Testing in an environment separate from the production environment; and
(iv) Put in place an escrow arrangement in case where third-party vendors develop mobile apps but the source codes are not released to the Company.
(i). The Company shall be responsible for development of a standard architecture based on set of security principles, rules, techniques, processes, and patterns to design a secure App;
(ii). The entire development of App shall revolve around the architecture principles, which can be updated based on the learnings during the course of development of application layers (or equivalent) and operational usage and consumer feedback;
(iii). The Company shall ensure that the App architecture is robust and scalable, commensurate with the application volumes and user growth. For this purpose, a robust capacity management plan shall be put in place to meet evolving demand.
(i). The Company shall implement a flexible device registration/binding functionality using multiple properties unique to the device (such as IP address, location, remote server, time of the day, device type, location, PIN code, Wi-Fi information, screen size, browser, etc.) so that only registered devices are allowed to access backend servers.
(ii). The device registration/binding shall preferably be implemented using a combination of hardware, software and service information. In case, multiple devices are registered by a user:
a) the user must be notified of every new device registration on the registered mobile number, email or phone call; and
b) The Company shall maintain record of all registered devices, providing the user a facility to disable a registered device.
(i). The Company shall ensure that explicit customer/user/unitholder/investor consent in a convenient manner is obtained before allowing registration of App;
(ii). A login authentication shall be in place.
(iii). The Company shall ensure that the access to personal data is protected by strong customer/user/unitholder/investor authentication mechanism including:
a) Implementation of multi-factor authentication (MFA) for registration of App user-account;
b) Strong and configurable PIN/password/pattern or a biometric credential such as face recognition or fingerprint recognition;
c) Time-based one-time passwords (TOTP) for authentication;
d) OTP auto-fetching functionality. The validity of OTP shall not exceed more than 180 seconds;
e) Configure maximum number of failed attempts of authentication after which access to the app is blocked;
f) Define maximum duration for termination of inactive mobile service sessions. Maximum duration for termination of inactive mobile service sessions shall not exceed thirty minutes;
g) Ensuring that user authentication shall be processed only at the app owner’s server-end; and
h) Ensure that authentication attempts are logged and monitored to detect login anomalies and possible breaches.
(i). The Company shall ensure that sensitive information is not stored in a shared store segment with other App on mobile devices. It is recommended to utilize only the device internal storage, which is virtually sandboxed per app or preferably in a container app without meddling with other applications or security settings of the mobile devices;
(ii). The Company shall ensure that the App erase/expire all application specific sensitive data stored in all temporary and permanent memories of the device during logoff or on termination of app instance. This requirement shall not apply to user-initiated downloads or reports (e.g., transaction history) saved locally on the device by the user.
(iii). Customer credentials and transactional data shall be encrypted while in-transit and at rest using strong, internationally accepted and published standards for key length, algorithms, cipher suites, digital certificates and applicable protocols that are not deprecated/ demonstrated to be insecure/vulnerable;
(iv). Encryption keys shall only be stored with appropriate robust security controls and shall remain in a non-exportable form in a highly secure and standard key store. It may be bound to the secure hardware (e.g. Trusted Execution Environment, Secure Element for Android or its equivalent on any other platform). Further, Key Use Authorization shall be implemented, which should not be changed after generation of keys.
(i). The Company shall ensure to enforce secure communication during the session establishment, exchange of data among App and backend services (including microservices);
(ii). Transport layer encryption shall be implemented for all communications between the App and app servers.
(iii). The Company shall setup their own Trust Manager to avoid accepting every unknown certificate. App shall use valid certificates issued by a trusted certificate authority;
(iv). App shall have inbuilt controls to mitigate bypassing of certificate pinning;
(v). App shall cease operations until certification errors are properly addressed;
(vi). The Company shall ensure that App must be able to identify new network connections and appropriate controls shall be implemented under such circumstances;
(i). The Company shall ensure that App has automatic user-logoff functionality after a configurable idle time-period not exceeding thirty minutes;
(ii). The Company shall ensure that App has an easy to use and clearly visible logoff method;
(iii). The Company shall ensure that App erase/expire all application specific sensitive data stored in all temporary and permanent memories of the device during logoff or on termination of app instance;
(iv). The Company shall ensure that a procedure is in place to detect multiple simultaneous login attempts and immediately communicate it to the concerned user through alternate channels such as callback, SMS, email etc.
(i). The Company shall implement necessary checks on the server-side to verify App integrity and to detect any manipulation.
(ii). The Company shall ensure that installation of App is not allowed on rooted/jail broken devices;
NIC Building, 63 Jinnah Avenue, Blue Area, Islamabad.
Tel: 051-9207091-4, Fax. No. 051-9100473
```
```markdown
SECURITIES AND EXCHANGE COMMISSION OF PAKISTAN SPECIALIZED COMPANIES DIVISION FUND MANAGEMENT DEPARTMENT
(iii). The Company shall ensure that App is not allowed to run inside a debugger/emulator. For this purpose, App shall have debugger/emulator detections in place. Further, The Company shall not allow any third party to debug the application during runtime.
H. App Permissions
(i). The Company shall ensure to restrict data shared with other applications on the device through fine-grained permissions; (ii). The Company shall ensure to minimize the number of permissions requested by the app and ensure that the permissions correlate to functionality required for the app to work. App shall defer or relinquish permissions when the same are no longer needed; (iii). Unless for a specific business requirement in accordance with the security architecture principles, the Company shall restrict navigation from the App to external applications, websites or untrusted content, unless explicitly required for a business function and in accordance with the Company’s approved security architecture principles.
I. Secure Coding
(i). The Company shall ensure that their App developers adhere to industry accepted secure coding practices and standards; (ii). The Company shall ensure that security libraries offered by mobile operating systems are correctly designed and implemented and that the cipher suites they support are sufficiently strong. Accordingly, The Company shall only use necessary and secure services, protocols, components, and dependent software and hardware, including those provided by third parties. (iii). The Company shall document all required protocols, services, components, and dependent software and hardware that are necessary for any functionality of the application. (iv). The Company shall have knowledge of all off-the-shelf libraries/modules/components utilized in the development of App; (v). The Company shall ensure that code signing is used for the App to confirm the software author and guarantee that the code has not been altered or corrupted since it was signed; (vi). The Company shall ensure that private key used for code signing is generated, securely stored and appropriately backed-up; (vii). The Company shall ensure that minification and source code obfuscation techniques are used in the App; (viii). The Company shall ensure to review application code prior to release to customers after any significant change, to identify any potential coding vulnerabilities; (ix). The Company shall verify that App is not vulnerable to common coding vulnerabilities by performing manual or automated penetration testing that specifically attempts to exploit injection flaws, buffer overflow, insecure cryptographic storage, insecure communications and improper error handling etc.
J. Input and Output Handling
(i). The Company shall ensure that any input coming from the client that is to be stored in databases is properly validated to avoid SQL injection attacks; (ii). The Company shall ensure that input and output data is properly sanitized and validated at the server and at the client-end; (iii). Auto-complete feature shall be disabled for sensitive information such as login IDs and passwords; (iv). Clipboard/copy-paste function shall be disabled for sensitive data. The Company may also use in-app keypad/ keyboard to capture the input from users.
K. Error and Exception Handling
(i). App shall have a proper error-handling mechanism and all errors shall be logged in the server; and (ii). Sensitive information and/or hints shall not be disclosed in error/warning messages and notifications.
L. Monitoring, Logs and Data Leakage
(i). The Company shall ensure that the app usage behavior is maintained and monitored through automated mechanism and deploy tools to identify any anomaly in the usage and behavior. The mechanism shall integrate with complete process of customer support for verification to clear the anomaly for consumer protection;
NIC Building, 63 Jinnah Avenue, Blue Area, Islamabad.
Tel: 051-9207091-4, Fax. No. 051-9100473
```
```markdown
(Format of Gender Disaggregated Data)
[See Clause 3.1(c)]
Name of AMC/Digital AMC:
License Type:
Name of App:
Reporting Month
| No. of users registered/onboarded | No. of Investment Transactions Executed | Total Amount Invested | Total Amount Redeemed | Net Amount of Investment |
|---|---|---|---|---|
| Male | Male | Male | Male | Male |
| Female | Female | Female | Female | Female |
| No. of users registered/onboarded | No. of Investment Transactions Executed | Total Amount Invested | Total Amount Redeemed | Net Amount of Investment |
|---|---|---|---|---|
| Male | Male | Male | Male | Male |
| Female | Female | Female | Female | Female |
| Description | As end of Month, |
|---|---|
| Assets under Management | |
| Active UIN | |
| Avg Amount of Investment per UIN |
| No. of downloads | Registered Users | No. of Verified UIN | % of user retention |
|---|---|---|---|
NIC Building, 63 Jinnah Avenue, Blue Area, Islamabad.
Tel: 051-9207091-4, Fax. No. 051-9100473
Code of Conduct for Call Centers by the Digital Asset Management Company (Company) [See Clause (3.1)(f)]
(i). The Company shall have a comprehensive policy and Standard Operating Procedures (SOP) on call center management duly approved by their Board of Directors;
(ii). Display, at conspicuous position on Company’s websites/digital Apps/digital channel, the approved Policy and SOPs, as required under Clause (i) of this Code.
(iii). Ensure that call center numbers are displayed prominently on Company’s websites/digital Apps/digital channel. Moreover, the companies are encouraged to deploy toll-free numbers for their call centers;
(iv). Customers/user/unitholder/investors must be given the choice to select their preferred language between Urdu or English;
(v). Agents must not refuse to lodge complaint of the customer/user/unitholder/investor;
(vi). Complaints received through the call center are properly recorded in the Complaint Management System (CMS), preferably through appropriate automation;
(vii). The Company must ensure the confidentiality of customer’s data shared with the call center agents through appropriate oversight and security clauses in employment contract;
(viii). The company must ensure to implement direct dialing call center solutions, wherein the customer/user/unitholder/investors are contacted without exposure of their number or confidential data to the contacting staff;
(ix). Ensure periodic trainings of their call center staff on product features, approved SOPs and regulatory frameworks to avoid mis-selling and breach of regulatory requirements;
(x). The Company shall mandate periodic reporting on performance of call centers including Complaint Management turnaround time (TAT);
(xi). The Company shall ensure that supervision function like quality assurance checks of call center should not be outsourced;
(xii). Conduct consumer testing/ consumer recalls at least on an annual basis to assess customer awareness regarding call centers and take actions for improvement where required;
(xiii). Call center agent/staff must treat all customers with respect, courtesy, and professionalism at all times;
(xiv). Offensive/threatening language, discriminatory remarks, or disrespectful behavior towards customers is strictly prohibited;
(xv). Agents maintain a level of professionalism throughout the entire conversation. All conversations should be in line with corporate values and goals;
(xvi). An objective professional tone should be used with customer to hear/register their complaint and a tentative TAT shall be shared with them for complaint resolution;
(xvii). Agents must avoid mis-selling, maligning other competitive market products and exaggerating facts to their benefit;
(xviii). Agents must ensure that customer/user/unitholder/investor are explicitly informed about their calls being recorded at the call center; and
(xix). Upon resolution of complaint within committed TAT customer should be intimated as such, in case the complaint remains unresolved, a call/email should be made to customer, depending upon the mode through which complaint was initially lodged, to update on the progress made and a revised TAT shall be shared with customer.
NIC Building, 63 Jinnah Avenue, Blue Area, Islamabad.
Tel: 051-9207091-4, Fax. No. 051-9100473
Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
RegAlert holds no document that amends or replaces this one. This is not a check that it is in force: confirm with the regulator.
“in exercise of its powers conferred under Section 282B(3) of the Companies Ordinance, 1984 (XLVII of 1984)”
“read with provisions of Regulation 67AL(a)(ii) of the Non-Banking Finance Companies and Notified Entities Regulations, 2008”
More like this from SECP
SECP published 4 documents in the last 30 days. We email you each new one the day it's published.
Source: Securities and Exchange Commission of Pakistan — original document · Summary generated with machine assistance and checked by an AI reviewer before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added · updated