Review managed transfer hosting as a service boundary
EFT Arcus is Globalscape's managed-file-transfer-as-a-service offering. It should be compared with on-premises EFT through operating responsibilities, permitted configuration and data handling, not simply as the same installation in another building. The current service definition and documented limits belong in the procurement review.
Identify partners, transfer workflows and the information that will pass through or remain in the service. Determine who approves hosting and access arrangements for the organisation. A cloud service may reduce some infrastructure tasks while leaving customer ownership of accounts, transfer rules and information decisions intact.
Confirm entitlements before importing production exchanges
Request current Arcus documentation for available features, administration, support and service commitments. Establish customer and provider duties, including certificates, identity integration and any change restrictions. Do not infer unlimited configuration or a particular availability or response guarantee from the service name.
Pilot partner onboarding and a representative workflow with approved files. Test completion evidence, an unavailable destination and the customer-visible escalation route. Review how records can be exported or moved if the service changes later. Handover should include the responsibility matrix, transfer definitions and operating contacts. UAE procurement teams should approve processing location and related requirements through their authorised advisers before live information is introduced.
Evidence to request for this scope
- Obtain current service terms, permitted configuration and customer administration boundaries.
- Validate partner onboarding, transfer completion and a failed-delivery escalation.
- Document data handling, exit requirements and responsibility for continuing workflow changes.