Connector registry
A sandbox connector is not a live integration
No live integration is claimed until an authorised end-to-end exchange has been verified. Every capability below states the exact approval, interface documentation, credential or network access still missing.
Registry totals
Punjab Safe Cities Authority (intended target)
- Legal entity
- Punjab Safe Cities Authority (intended target)
- Trading name
- Punjab Safe City
- Kind
- Safe City
- Jurisdiction
- Punjab
- City / district endpoints
- 6
- Emergency contact centreRequires authorisationProductioncon-org-safe-punjab-contact_centre
Intended integration: Receive permitted incident records and supporting attachments
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's contact_centre 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.
- Dispatch / resource managementRequires authorisationProductioncon-org-safe-punjab-dispatch
Intended integration: Request a dispatch decision and receive authorised response updates
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's dispatch 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.
- Event bus / integration gatewayRequires authorisationProductioncon-org-safe-punjab-event_bus
Intended integration: Exchange structured alerts and workflow events
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's event_bus 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.
- Event bus / integration gatewaySandboxSandbox · labelled simulatorcon-org-safe-punjab-simulator
Intended integration: Exchange structured alerts and workflow events
- Vendor
- AETNIC simulator
- Environment
- Sandbox (labelled simulator)
- Interface version
- sim-1.0
- Authentication
- none (local simulator)
- Permitted read ops
- receiveStatusEvent
- Permitted write ops
- createOperationalTicket, getRequestStatus
- Data-sharing agreement
- None recorded
- Data classification
- Internal
- Rate limits
- none (local)
- Health-check method
- always healthy
- Support owner
- AETNIC delivery team
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities 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.
- Evidence managementRequires authorisationProductioncon-org-safe-punjab-evidence_management
Intended integration: Transfer approved evidence packages and preserve provenance
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's evidence_management 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.
- GISRequires authorisationProductioncon-org-safe-punjab-gis
Intended integration: Display approved incident locations, jurisdiction boundaries and operational zones
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's gis 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.
- Identity providerRequires authorisationProductioncon-org-safe-punjab-identity_provider
Intended integration: Federated authentication and role mapping where supported
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's identity_provider 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 management / CADRequires authorisationProductioncon-org-safe-punjab-incident_cad
Intended integration: Create approved incidents, receive acknowledgements and synchronise status
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's incident_cad 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.
- Video management (VMS)Requires authorisationProductioncon-org-safe-punjab-vms
Intended integration: Reference authorised cameras and retrieve incident-specific clips
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Punjab Safe Cities Authority (intended target); (2) the vendor's vms 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.
Sindh Safe City programme (intended target)
- Legal entity
- Sindh Safe City programme (intended target)
- Trading name
- Sindh Safe City
- Kind
- Safe City
- Jurisdiction
- Sindh
- City / district endpoints
- 4
- Emergency contact centreRequires authorisationProductioncon-org-safe-sindh-contact_centre
Intended integration: Receive permitted incident records and supporting attachments
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's contact_centre 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.
- Dispatch / resource managementRequires authorisationProductioncon-org-safe-sindh-dispatch
Intended integration: Request a dispatch decision and receive authorised response updates
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's dispatch 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.
- Event bus / integration gatewayRequires authorisationProductioncon-org-safe-sindh-event_bus
Intended integration: Exchange structured alerts and workflow events
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's event_bus 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.
- Event bus / integration gatewaySandboxSandbox · labelled simulatorcon-org-safe-sindh-simulator
Intended integration: Exchange structured alerts and workflow events
- Vendor
- AETNIC simulator
- Environment
- Sandbox (labelled simulator)
- Interface version
- sim-1.0
- Authentication
- none (local simulator)
- Permitted read ops
- receiveStatusEvent
- Permitted write ops
- createOperationalTicket, getRequestStatus
- Data-sharing agreement
- None recorded
- Data classification
- Internal
- Rate limits
- none (local)
- Health-check method
- always healthy
- Support owner
- AETNIC delivery team
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (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.
- Evidence managementRequires authorisationProductioncon-org-safe-sindh-evidence_management
Intended integration: Transfer approved evidence packages and preserve provenance
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's evidence_management 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.
- GISRequires authorisationProductioncon-org-safe-sindh-gis
Intended integration: Display approved incident locations, jurisdiction boundaries and operational zones
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's gis 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.
- Identity providerRequires authorisationProductioncon-org-safe-sindh-identity_provider
Intended integration: Federated authentication and role mapping where supported
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's identity_provider 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 management / CADRequires authorisationProductioncon-org-safe-sindh-incident_cad
Intended integration: Create approved incidents, receive acknowledgements and synchronise status
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's incident_cad 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.
- Video management (VMS)Requires authorisationProductioncon-org-safe-sindh-vms
Intended integration: Reference authorised cameras and retrieve incident-specific clips
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Sindh Safe City programme (intended target); (2) the vendor's vms 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.
Khyber Pakhtunkhwa Safe City programme (intended target)
- Legal entity
- Khyber Pakhtunkhwa Safe City programme (intended target)
- Trading name
- KP Safe City
- Kind
- Safe City
- Jurisdiction
- Khyber Pakhtunkhwa
- City / district endpoints
- 4
- Emergency contact centreRequires authorisationProductioncon-org-safe-kpk-contact_centre
Intended integration: Receive permitted incident records and supporting attachments
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's contact_centre 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.
- Dispatch / resource managementRequires authorisationProductioncon-org-safe-kpk-dispatch
Intended integration: Request a dispatch decision and receive authorised response updates
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's dispatch 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.
- Event bus / integration gatewayRequires authorisationProductioncon-org-safe-kpk-event_bus
Intended integration: Exchange structured alerts and workflow events
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's event_bus 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.
- Event bus / integration gatewaySandboxSandbox · labelled simulatorcon-org-safe-kpk-simulator
Intended integration: Exchange structured alerts and workflow events
- Vendor
- AETNIC simulator
- Environment
- Sandbox (labelled simulator)
- Interface version
- sim-1.0
- Authentication
- none (local simulator)
- Permitted read ops
- receiveStatusEvent
- Permitted write ops
- createOperationalTicket, getRequestStatus
- Data-sharing agreement
- None recorded
- Data classification
- Internal
- Rate limits
- none (local)
- Health-check method
- always healthy
- Support owner
- AETNIC delivery team
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (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.
- Evidence managementRequires authorisationProductioncon-org-safe-kpk-evidence_management
Intended integration: Transfer approved evidence packages and preserve provenance
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's evidence_management 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.
- GISRequires authorisationProductioncon-org-safe-kpk-gis
Intended integration: Display approved incident locations, jurisdiction boundaries and operational zones
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's gis 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.
- Identity providerRequires authorisationProductioncon-org-safe-kpk-identity_provider
Intended integration: Federated authentication and role mapping where supported
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's identity_provider 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 management / CADRequires authorisationProductioncon-org-safe-kpk-incident_cad
Intended integration: Create approved incidents, receive acknowledgements and synchronise status
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's incident_cad 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.
- Video management (VMS)Requires authorisationProductioncon-org-safe-kpk-vms
Intended integration: Reference authorised cameras and retrieve incident-specific clips
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Khyber Pakhtunkhwa Safe City programme (intended target); (2) the vendor's vms 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.
Balochistan Safe City programme (intended target)
- Legal entity
- Balochistan Safe City programme (intended target)
- Trading name
- Balochistan Safe City
- Kind
- Safe City
- Jurisdiction
- Balochistan
- City / district endpoints
- 3
- Emergency contact centreRequires authorisationProductioncon-org-safe-balochistan-contact_centre
Intended integration: Receive permitted incident records and supporting attachments
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's contact_centre 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.
- Dispatch / resource managementRequires authorisationProductioncon-org-safe-balochistan-dispatch
Intended integration: Request a dispatch decision and receive authorised response updates
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's dispatch 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.
- Event bus / integration gatewayRequires authorisationProductioncon-org-safe-balochistan-event_bus
Intended integration: Exchange structured alerts and workflow events
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's event_bus 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.
- Event bus / integration gatewaySandboxSandbox · labelled simulatorcon-org-safe-balochistan-simulator
Intended integration: Exchange structured alerts and workflow events
- Vendor
- AETNIC simulator
- Environment
- Sandbox (labelled simulator)
- Interface version
- sim-1.0
- Authentication
- none (local simulator)
- Permitted read ops
- receiveStatusEvent
- Permitted write ops
- createOperationalTicket, getRequestStatus
- Data-sharing agreement
- None recorded
- Data classification
- Internal
- Rate limits
- none (local)
- Health-check method
- always healthy
- Support owner
- AETNIC delivery team
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (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.
- Evidence managementRequires authorisationProductioncon-org-safe-balochistan-evidence_management
Intended integration: Transfer approved evidence packages and preserve provenance
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's evidence_management 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.
- GISRequires authorisationProductioncon-org-safe-balochistan-gis
Intended integration: Display approved incident locations, jurisdiction boundaries and operational zones
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's gis 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.
- Identity providerRequires authorisationProductioncon-org-safe-balochistan-identity_provider
Intended integration: Federated authentication and role mapping where supported
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's identity_provider 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 management / CADRequires authorisationProductioncon-org-safe-balochistan-incident_cad
Intended integration: Create approved incidents, receive acknowledgements and synchronise status
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's incident_cad 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.
- Video management (VMS)Requires authorisationProductioncon-org-safe-balochistan-vms
Intended integration: Reference authorised cameras and retrieve incident-specific clips
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Balochistan Safe City programme (intended target); (2) the vendor's vms 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.
Islamabad Capital Territory Safe City project (intended target)
- Legal entity
- Islamabad Capital Territory Safe City project (intended target)
- Trading name
- Islamabad Safe City
- Kind
- Safe City
- Jurisdiction
- Islamabad Capital Territory
- City / district endpoints
- 1
- Emergency contact centreRequires authorisationProductioncon-org-safe-ict-contact_centre
Intended integration: Receive permitted incident records and supporting attachments
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's contact_centre 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.
- Dispatch / resource managementRequires authorisationProductioncon-org-safe-ict-dispatch
Intended integration: Request a dispatch decision and receive authorised response updates
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's dispatch 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.
- Event bus / integration gatewayRequires authorisationProductioncon-org-safe-ict-event_bus
Intended integration: Exchange structured alerts and workflow events
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's event_bus 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.
- Event bus / integration gatewaySandboxSandbox · labelled simulatorcon-org-safe-ict-simulator
Intended integration: Exchange structured alerts and workflow events
- Vendor
- AETNIC simulator
- Environment
- Sandbox (labelled simulator)
- Interface version
- sim-1.0
- Authentication
- none (local simulator)
- Permitted read ops
- receiveStatusEvent
- Permitted write ops
- createOperationalTicket, getRequestStatus
- Data-sharing agreement
- None recorded
- Data classification
- Internal
- Rate limits
- none (local)
- Health-check method
- always healthy
- Support owner
- AETNIC delivery team
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (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.
- Evidence managementRequires authorisationProductioncon-org-safe-ict-evidence_management
Intended integration: Transfer approved evidence packages and preserve provenance
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's evidence_management 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.
- GISRequires authorisationProductioncon-org-safe-ict-gis
Intended integration: Display approved incident locations, jurisdiction boundaries and operational zones
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's gis 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.
- Identity providerRequires authorisationProductioncon-org-safe-ict-identity_provider
Intended integration: Federated authentication and role mapping where supported
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's identity_provider 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 management / CADRequires authorisationProductioncon-org-safe-ict-incident_cad
Intended integration: Create approved incidents, receive acknowledgements and synchronise status
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's incident_cad 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.
- Video management (VMS)Requires authorisationProductioncon-org-safe-ict-vms
Intended integration: Reference authorised cameras and retrieve incident-specific clips
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Sensitive
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Islamabad Capital Territory Safe City project (intended target); (2) the vendor's vms 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.
Pakistan Telecommunication Company Limited (intended target)
- Legal entity
- Pakistan Telecommunication Company Limited (intended target)
- Trading name
- PTCL
- Kind
- ISP / telecom operator
- Jurisdiction
- Not set
- City / district endpoints
- 0
- Abuse reportingRequires agreementProductioncon-org-isp-ptcl-abuse_reporting
Intended integration: Submit reviewed evidence concerning fraud, threats or other defined abuse
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's abuse_reporting 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.
- Enterprise connectivityRequires credentialsProductioncon-org-isp-ptcl-enterprise_connectivity
Intended integration: View health of the customer's own contracted circuits
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's enterprise_connectivity 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 exchangeRequires agreementProductioncon-org-isp-ptcl-evidence_exchange
Intended integration: Transfer approved, minimum-necessary case evidence
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's evidence_exchange 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.
- Identity federationUnsupportedProductioncon-org-isp-ptcl-identity_federation
Intended integration: Authenticate authorised operator users through supported federation
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Pakistan Telecommunication Company Limited (intended target) publishes no federation interface this application can use. Requires an identity-federation arrangement agreed with the organisation as a precondition.
- Incident exchangeRequires agreementProductioncon-org-isp-ptcl-incident_exchange
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's incident_exchange 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 exchangeSandboxSandbox · labelled simulatorcon-org-isp-ptcl-simulator
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- AETNIC simulator
- Environment
- Sandbox (labelled simulator)
- Interface version
- sim-1.0
- Authentication
- none (local simulator)
- Permitted read ops
- receiveStatusEvent
- Permitted write ops
- createOperationalTicket, getRequestStatus
- Data-sharing agreement
- None recorded
- Data classification
- Internal
- Rate limits
- none (local)
- Health-check method
- always healthy
- Support owner
- AETNIC delivery team
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (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.
- Request trackingRequires agreementProductioncon-org-isp-ptcl-request_tracking
Intended integration: Track official requests and operator responses without assuming implementation authority
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's request_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.
- Service assuranceRequires credentialsProductioncon-org-isp-ptcl-service_assurance
Intended integration: Receive outages, maintenance notices and restoration updates
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's service_assurance 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.
- SLA reportingManual submissionProductioncon-org-isp-ptcl-sla_reporting
Intended integration: Compare observed ticket milestones against configured contractual targets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Company Limited (intended target); (2) the vendor's sla_reporting 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.
Transworld (intended target)
- Legal entity
- Transworld (intended target)
- Trading name
- Transworld
- Kind
- ISP / telecom operator
- Jurisdiction
- Not set
- City / district endpoints
- 0
- Abuse reportingRequires agreementProductioncon-org-isp-transworld-abuse_reporting
Intended integration: Submit reviewed evidence concerning fraud, threats or other defined abuse
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's abuse_reporting 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.
- Enterprise connectivityRequires credentialsProductioncon-org-isp-transworld-enterprise_connectivity
Intended integration: View health of the customer's own contracted circuits
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's enterprise_connectivity 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 exchangeRequires agreementProductioncon-org-isp-transworld-evidence_exchange
Intended integration: Transfer approved, minimum-necessary case evidence
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's evidence_exchange 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.
- Identity federationUnsupportedProductioncon-org-isp-transworld-identity_federation
Intended integration: Authenticate authorised operator users through supported federation
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Transworld (intended target) publishes no federation interface this application can use. Requires an identity-federation arrangement agreed with the organisation as a precondition.
- Incident exchangeRequires agreementProductioncon-org-isp-transworld-incident_exchange
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's incident_exchange 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 exchangeSandboxSandbox · labelled simulatorcon-org-isp-transworld-simulator
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- AETNIC simulator
- Environment
- Sandbox (labelled simulator)
- Interface version
- sim-1.0
- Authentication
- none (local simulator)
- Permitted read ops
- receiveStatusEvent
- Permitted write ops
- createOperationalTicket, getRequestStatus
- Data-sharing agreement
- None recorded
- Data classification
- Internal
- Rate limits
- none (local)
- Health-check method
- always healthy
- Support owner
- AETNIC delivery team
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Transworld (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.
- Request trackingRequires agreementProductioncon-org-isp-transworld-request_tracking
Intended integration: Track official requests and operator responses without assuming implementation authority
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's request_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.
- Service assuranceRequires credentialsProductioncon-org-isp-transworld-service_assurance
Intended integration: Receive outages, maintenance notices and restoration updates
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's service_assurance 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.
- SLA reportingManual submissionProductioncon-org-isp-transworld-sla_reporting
Intended integration: Compare observed ticket milestones against configured contractual targets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Transworld (intended target); (2) the vendor's sla_reporting 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.
Nayatel (intended target)
- Legal entity
- Nayatel (intended target)
- Trading name
- Nayatel
- Kind
- ISP / telecom operator
- Jurisdiction
- Not set
- City / district endpoints
- 0
- Abuse reportingRequires agreementProductioncon-org-isp-nayatel-abuse_reporting
Intended integration: Submit reviewed evidence concerning fraud, threats or other defined abuse
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's abuse_reporting 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.
- Enterprise connectivityRequires credentialsProductioncon-org-isp-nayatel-enterprise_connectivity
Intended integration: View health of the customer's own contracted circuits
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's enterprise_connectivity 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 exchangeRequires agreementProductioncon-org-isp-nayatel-evidence_exchange
Intended integration: Transfer approved, minimum-necessary case evidence
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's evidence_exchange 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.
- Identity federationUnsupportedProductioncon-org-isp-nayatel-identity_federation
Intended integration: Authenticate authorised operator users through supported federation
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Nayatel (intended target) publishes no federation interface this application can use. Requires an identity-federation arrangement agreed with the organisation as a precondition.
- Incident exchangeRequires agreementProductioncon-org-isp-nayatel-incident_exchange
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's incident_exchange 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 exchangeSandboxSandbox · labelled simulatorcon-org-isp-nayatel-simulator
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- AETNIC simulator
- Environment
- Sandbox (labelled simulator)
- Interface version
- sim-1.0
- Authentication
- none (local simulator)
- Permitted read ops
- receiveStatusEvent
- Permitted write ops
- createOperationalTicket, getRequestStatus
- Data-sharing agreement
- None recorded
- Data classification
- Internal
- Rate limits
- none (local)
- Health-check method
- always healthy
- Support owner
- AETNIC delivery team
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- SIMULATOR — not a live connection. Demonstrates the workflow only. To go live: Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (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.
- Request trackingRequires agreementProductioncon-org-isp-nayatel-request_tracking
Intended integration: Track official requests and operator responses without assuming implementation authority
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's request_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.
- Service assuranceRequires credentialsProductioncon-org-isp-nayatel-service_assurance
Intended integration: Receive outages, maintenance notices and restoration updates
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's service_assurance 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.
- SLA reportingManual submissionProductioncon-org-isp-nayatel-sla_reporting
Intended integration: Compare observed ticket milestones against configured contractual targets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Nayatel (intended target); (2) the vendor's sla_reporting 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.
Pakistan Telecommunication Authority (intended target)
- Legal entity
- Pakistan Telecommunication Authority (intended target)
- Trading name
- PTA
- Kind
- Regulator
- Jurisdiction
- Not set
- City / district endpoints
- 0
- Abuse reportingManual submissionProductioncon-org-regulator-pta-abuse_reporting
Intended integration: Submit reviewed evidence concerning fraud, threats or other defined abuse
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's abuse_reporting 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.
- Enterprise connectivityManual submissionProductioncon-org-regulator-pta-enterprise_connectivity
Intended integration: View health of the customer's own contracted circuits
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's enterprise_connectivity 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 exchangeManual submissionProductioncon-org-regulator-pta-evidence_exchange
Intended integration: Transfer approved, minimum-necessary case evidence
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's evidence_exchange 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.
- Identity federationManual submissionProductioncon-org-regulator-pta-identity_federation
Intended integration: Authenticate authorised operator users through supported federation
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's identity_federation 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 exchangeManual submissionProductioncon-org-regulator-pta-incident_exchange
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's incident_exchange 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 exchangeSandboxSandbox · labelled simulatorcon-org-regulator-pta-simulator
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- AETNIC simulator
- Environment
- Sandbox (labelled simulator)
- Interface version
- sim-1.0
- Authentication
- none (local simulator)
- Permitted read ops
- receiveStatusEvent
- Permitted write ops
- createOperationalTicket, getRequestStatus
- Data-sharing agreement
- None recorded
- Data classification
- Internal
- Rate limits
- none (local)
- Health-check method
- always healthy
- Support owner
- AETNIC delivery team
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- 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.
- Request trackingManual submissionProductioncon-org-regulator-pta-request_tracking
Intended integration: Track official requests and operator responses without assuming implementation authority
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's request_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.
- Service assuranceManual submissionProductioncon-org-regulator-pta-service_assurance
Intended integration: Receive outages, maintenance notices and restoration updates
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's service_assurance 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.
- SLA reportingManual submissionProductioncon-org-regulator-pta-sla_reporting
Intended integration: Compare observed ticket milestones against configured contractual targets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Pakistan Telecommunication Authority (intended target); (2) the vendor's sla_reporting 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.
National Cyber Crime Investigation Agency (intended target)
- Legal entity
- National Cyber Crime Investigation Agency (intended target)
- Trading name
- NCCIA
- Kind
- Federal agency
- Jurisdiction
- Not set
- City / district endpoints
- 0
- Abuse reportingManual submissionProductioncon-org-federal-nccia-abuse_reporting
Intended integration: Submit reviewed evidence concerning fraud, threats or other defined abuse
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's abuse_reporting 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.
- Enterprise connectivityManual submissionProductioncon-org-federal-nccia-enterprise_connectivity
Intended integration: View health of the customer's own contracted circuits
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's enterprise_connectivity 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 exchangeManual submissionProductioncon-org-federal-nccia-evidence_exchange
Intended integration: Transfer approved, minimum-necessary case evidence
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's evidence_exchange 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.
- Identity federationManual submissionProductioncon-org-federal-nccia-identity_federation
Intended integration: Authenticate authorised operator users through supported federation
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's identity_federation 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 exchangeManual submissionProductioncon-org-federal-nccia-incident_exchange
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's incident_exchange 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 exchangeSandboxSandbox · labelled simulatorcon-org-federal-nccia-simulator
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- AETNIC simulator
- Environment
- Sandbox (labelled simulator)
- Interface version
- sim-1.0
- Authentication
- none (local simulator)
- Permitted read ops
- receiveStatusEvent
- Permitted write ops
- createOperationalTicket, getRequestStatus
- Data-sharing agreement
- None recorded
- Data classification
- Internal
- Rate limits
- none (local)
- Health-check method
- always healthy
- Support owner
- AETNIC delivery team
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- 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.
- Request trackingManual submissionProductioncon-org-federal-nccia-request_tracking
Intended integration: Track official requests and operator responses without assuming implementation authority
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's request_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.
- Service assuranceManual submissionProductioncon-org-federal-nccia-service_assurance
Intended integration: Receive outages, maintenance notices and restoration updates
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's service_assurance 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.
- SLA reportingManual submissionProductioncon-org-federal-nccia-sla_reporting
Intended integration: Compare observed ticket milestones against configured contractual targets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with National Cyber Crime Investigation Agency (intended target); (2) the vendor's sla_reporting 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.
Ministry of Interior, Pakistan (intended target)
- Legal entity
- Ministry of Interior, Pakistan (intended target)
- Trading name
- MOI
- Kind
- Federal agency
- Jurisdiction
- Not set
- City / district endpoints
- 0
- Abuse reportingManual submissionProductioncon-org-federal-moi-abuse_reporting
Intended integration: Submit reviewed evidence concerning fraud, threats or other defined abuse
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's abuse_reporting 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.
- Enterprise connectivityManual submissionProductioncon-org-federal-moi-enterprise_connectivity
Intended integration: View health of the customer's own contracted circuits
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's enterprise_connectivity 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 exchangeManual submissionProductioncon-org-federal-moi-evidence_exchange
Intended integration: Transfer approved, minimum-necessary case evidence
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's evidence_exchange 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.
- Identity federationManual submissionProductioncon-org-federal-moi-identity_federation
Intended integration: Authenticate authorised operator users through supported federation
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's identity_federation 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 exchangeManual submissionProductioncon-org-federal-moi-incident_exchange
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's incident_exchange 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 exchangeSandboxSandbox · labelled simulatorcon-org-federal-moi-simulator
Intended integration: Create, acknowledge and update operational tickets
- Vendor
- AETNIC simulator
- Environment
- Sandbox (labelled simulator)
- Interface version
- sim-1.0
- Authentication
- none (local simulator)
- Permitted read ops
- receiveStatusEvent
- Permitted write ops
- createOperationalTicket, getRequestStatus
- Data-sharing agreement
- None recorded
- Data classification
- Internal
- Rate limits
- none (local)
- Health-check method
- always healthy
- Support owner
- AETNIC delivery team
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- 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.
- Request trackingManual submissionProductioncon-org-federal-moi-request_tracking
Intended integration: Track official requests and operator responses without assuming implementation authority
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's request_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.
- Service assuranceManual submissionProductioncon-org-federal-moi-service_assurance
Intended integration: Receive outages, maintenance notices and restoration updates
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's service_assurance 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.
- SLA reportingManual submissionProductioncon-org-federal-moi-sla_reporting
Intended integration: Compare observed ticket milestones against configured contractual targets
- Vendor
- —
- Environment
- Production
- Interface version
- Not documented
- Authentication
- None recorded
- Permitted read ops
- None permitted
- Permitted write ops
- None permitted
- Data-sharing agreement
- None recorded
- Data classification
- Restricted
- Rate limits
- Not published
- Health-check method
- None recorded
- Support owner
- Unassigned
- Last successful exchange
- None — never verified live
- Credential / certificate expiry
- None recorded
- Acknowledgement capable
- Yes
- Verification capable
- No
- Verification evidence
- None recorded
- Blocking dependency
- Requires: (1) a signed data-sharing or interconnection agreement with Ministry of Interior, Pakistan (intended target); (2) the vendor's sla_reporting 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.