SANDBOX
Specialised agency modules

PTA · NCCIA · Ministry of Interior

Each agency is a separate workspace with its own referral register, incoming correspondence, deadlines and disclosure rules — not an operator connection. You are acting as operator.

How cross-agency sharing works here

A case reference never shares a case's contents. A transfer happens only through an approved disclosure that names the recipient unit, the purpose and the exact fields shared, and a transfer is not complete until a receipt is recorded. Nothing is broadcast to every organisation. An incoming document never authorises action by itself: a human must verify its authenticity, stated scope and intended recipient first. A complaint, referral or acknowledgement is never represented as a binding direction, and deadlines are reported only where one was actually documented.
Regulatory coordination and request management

PTA — Pakistan Telecommunication Authority

identity NOT verifiedManual submission7 categories configured · 0 open referral(s) · 0 awaiting acknowledgement · 0 document(s) awaiting verification · 0 briefing(s) · 0 disclosure(s)
  • Not a subscriber-information channel: no subscriber identity resolution is available or attempted.
  • A complaint, referral or acknowledgement is never represented as a binding direction.
  • No machine interface is assumed — submissions default to a tracked manual package until a receipt is recorded.

Agency categories (from the connector registry)

  • Reviewed abuse-report referralManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's abuse_report_referral interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Clarification / evidence requestManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's clarification_request interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Tracking a formally received directionManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's directions_tracking interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Operator incident coordinationManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's operator_incident_coordination interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Regulatory correspondenceSandbox

    SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Regulatory correspondenceManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's regulatory_correspondence interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Telecom service complaint / escalationManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's telecom_service_complaint interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

Referral register (0)

No referrals yet

Reviewed referrals to this agency appear here with their approvals, receipts and outcome. A prepared referral is not a submitted complaint.

6 agency categories. Verified live: 0.

Cybercrime referral and evidence preservation

NCCIA — National Cyber Crime Investigation Agency

identity NOT verifiedManual submission4 categories configured · 0 open referral(s) · 0 awaiting acknowledgement · 0 document(s) awaiting verification · 0 briefing(s) · 4 disclosure(s)
  • A connection does not confer investigative authority or access to government records.
  • A prepared referral is not a submitted complaint; a receipt is not acceptance for investigation.
  • An external case number is only ever recorded from the receiving authority.

Agency categories (from the connector registry)

  • Cybercrime referralSandbox

    SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Cybercrime referralManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's cybercrime_referral interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Evidence preservation requestManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's evidence_preservation_request interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Investigation correspondenceManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's investigation_correspondence interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

Referral register (0)

No referrals yet

Reviewed referrals to this agency appear here with their approvals, receipts and outcome. A prepared referral is not a submitted complaint.

Controlled disclosures (4)

  • → NCCIA Cybercrime Wingrefused

    Case-linked referral to the responsible authority · fields: case reference, incident category, evidence hash

  • → NCCIA Cybercrime Wingtransferred

    Case-linked referral to the responsible authority · fields: case reference

  • → NCCIA Cybercrime Wingtransferred

    Case-linked referral to the responsible authority · fields: case reference

  • → NCCIA Cybercrime Wingrefused

    Case-linked referral to the responsible authority · fields: case reference, incident category, evidence hash

3 agency categories. Verified live: 0.

Coordination, briefing and task register

MOI — Ministry of Interior, Pakistan

identity NOT verifiedManual submission5 categories configured · 0 open referral(s) · 0 awaiting acknowledgement · 0 document(s) awaiting verification · 0 briefing(s) · 4 disclosure(s)
  • No assumption that MOI holds direct operational authority over every connected organisation.
  • No political-sentiment surveillance, religious-community profiling or loyalty scoring.
  • Population-level conclusions are never inferred from an unrepresentative sample.

Agency categories (from the connector registry)

  • Correspondence & task registerManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's correspondence_task_register interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Incident briefingSandbox

    SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's the organisation's interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Incident briefingManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's incident_briefing interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Inter-agency referralManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's inter_agency_referral interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

  • Situation reportManual submission

    Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's situation_report interface documentation and its version; (3) credentials or certificates issued to THIS application; (4) network access / allowlisting to the receiving endpoint. None of the four is in place.

Referral register (0)

No referrals yet

Reviewed referrals to this agency appear here with their approvals, receipts and outcome. A prepared referral is not a submitted complaint.

Controlled disclosures (4)

  • → Interior Coordination Unittransferred

    Statutory correspondence · fields: case reference, incident category

  • → Interior Coordination Unittransferred

    Statutory correspondence · fields: case reference, incident category

  • → Interior Coordination Unittransferred

    Statutory correspondence · fields: case reference, incident category

  • → Interior Coordination Unittransferred

    Statutory correspondence · fields: case reference, incident category

4 agency categories. Verified live: 0.

Closed list

Permitted disclosure purposes

  • Case-linked referral to the responsible authority
  • Clarification requested by the recipient
  • Statutory correspondence
  • Operator service restoration for joint infrastructure

A disclosure outside this list is not preparable. Approval binds to the recipient, the purpose and the field list; a material change to any of them invalidates the approval.