IT that keeps entries filing, records retrievable, your license clean.IT that keeps entriesfilingrecordsretrievableyourlicenseclean
Your broker license depends on records and supervision. We keep the systems behind both organized, protected and ready for review.
Customs brokerage
Records that answer to CBP
Brokers live under rules most businesses never see. Your records have retention requirements, your employees work under your responsible supervision and control, and CBP expects to hear from you if those records are breached. That turns ordinary IT choices into compliance choices. Here’s where brokerages get exposed, and how we close it.
01 · The pressure
Every entry draws on regulated records
Cargo is sitting at the port and the importer wants it released. Your team classifies, values and files through ABI, pays duties, answers CBP queries and archives everything behind the entry. Those records have to stay retrievable for years and producible on request. If your entry software is down, cargo sits and storage charges pile up. If importer records leak, you’re dealing with clients, CBP and possibly a license review all at once.
- ABI filing stalls when entry software is down
- Records must stay producible on CBP request
- Importer identities and POAs carry real risk
CBP ACE PortalCargoWiseDescartesMagaya Customs ComplianceE2open Global Trade ManagementMicrosoft 365
02 · How it breaks
Shared ACE logins and scanned POAs in inboxes
Brokerage incidents usually start with convenience. One ACE portal login used by the whole team. Powers of attorney scanned and left in email attachments for years. A filer’s mailbox phished, giving an attacker importer numbers, which for sole proprietors can be Social Security numbers. An old server holding archived entry packets with no tested backup. A departing employee who still has access to client files a month later.
- Shared portal credentials across filers
- POAs and importer IDs buried in email
- Archived entry packets with untested backups
CBP ACE PortalCargoWiseDescartesMagaya Customs ComplianceE2open Global Trade ManagementMicrosoft 365
03 · What we change
Named access, structured records, a breach plan
Every filer and portal user gets a named account with MFA, so access lines up with the people you supervise. Entry packets, POAs and correspondence move into structured document storage with retention settings, encryption and audit logs. We back up the entry system and archives to immutable storage and test restores. Mailboxes get phishing defenses. And we write an incident plan that includes the CBP breach notification step, coordinated with your counsel.
- Named, MFA-protected accounts for every filer
- Retention-aware document storage with audit logs
- Incident plan that includes CBP notification
CBP ACE PortalCargoWiseDescartesMagaya Customs ComplianceE2open Global Trade ManagementMicrosoft 365
04 · The after
A records request is a search, not a scramble
When CBP asks for records behind an entry, you search, export and send. When a large importer’s compliance team asks how you protect their data, you hand over a short security summary and an access review. Your licensed broker can see who touched which client file, which is real evidence of supervision. And if an incident happens, you already know the first hour: who to call, what to preserve and when CBP hears about it.
- Records produced quickly on request
- Access logs that show supervision in practice
- A rehearsed first hour if a breach happens
CBP ACE PortalCargoWiseDescartesMagaya Customs ComplianceE2open Global Trade ManagementMicrosoft 365