Safety Norms: Securities Trading and Derivatives

1Purpose, Scope, and Safety Principles

These norms protect the firm, its clients, its counterparties, and the wider market from harm caused by trading activity. In this subject, safety means controlled exposure to financial, operational, legal, and conduct risk. It is not a generic workplace safety topic, although physical security of trading floors, equipment, and storage media is included.

Scope covers securities such as equities, bonds, and funds, and derivatives such as futures, options, swaps, and forwards. It applies across front office trading, middle office risk and confirmation, back office settlement and reconciliation, and compliance and technology support. This is educational guidance. It does not replace licensing, formal training, approved firm policies, supervision, or advice from legal and compliance counsel.

• Mandatory: no trade may be entered, amended, or cancelled outside a documented trading mandate and approved limits.
• Mandatory: client, firm, and market information must be handled under the confidentiality rules that apply to the person's role.
• Recommended: review these norms at least annually against current rules, local procedures, and incident findings.

2Roles, Competence, and Accountability

Senior management owns the control framework and approves risk appetite, trading mandates, and limit structures. The head of trading supervises front office conduct. The independent risk function monitors exposures and limit usage. The compliance function monitors regulatory obligations and surveillance alerts. Operations and finance teams own confirmation, settlement, collateral, and reconciliation. Technology owns access controls and system change management.

Competence is a precondition for access. Each person should hold any licenses or registrations required by the jurisdiction and product, and should be authorized in writing for the instruments, desks, and systems they use. Access is granted by role, not by seniority. Verify licensing status against the relevant regulator register and internal records before granting access. Do not assume a colleague is licensed because they have worked on a desk for years.

• Mandatory: no one trades, approves, or releases payments without a documented authorization for that product and limit.
• Mandatory: unauthorized staff must never place orders on another person's behalf or use their credentials.
• Recommended: maintain a responsibilities matrix naming the owner of each control, reviewed by compliance at least annually.

3Course-Specific Hazards and Risk Assessment

Typical activities include order entry and execution, quoting and market making, hedging with futures and options, margin and collateral management, trade confirmation and affirmation, settlement and reconciliation, position valuation, and client reporting. Common tools include order management systems, execution platforms, pricing models, risk engines, market data feeds, clearing and custody links, chat and email channels, and spreadsheets used for calculations.

Each hazard should receive a risk rating based on likelihood and impact, using a scale approved by the risk function. Realistic examples include: order entry errors, sometimes called fat-finger errors, where the wrong size, price, or instrument is sent, rated high because losses can build within minutes; unauthorized trading, rated high; valuation error on complex derivatives, rated high; missed margin or collateral calls, rated high; leakage of material non-public information, rated high; reconciliation breaks, rated medium; misleading client communications, rated medium to high; and spreadsheet error in risk or pricing calculations, rated medium.

• Hazard: order sent with wrong quantity, price, or instrument. Control: pre-trade price and size checks, plus second confirmation for orders above a set threshold.
• Hazard: algorithm behaves outside design. Control: kill switch held by named staff, with tested disconnection steps.
• Hazard: spreadsheet used as system of record. Control: only validated, access-controlled spreadsheets may support calculations, and they must be reconciled to source systems.

4Preventive Controls and Safe Trading Practices

Preventive controls work in layers. Pre-trade controls block orders that breach price collars, size limits, or restricted lists. Intraday monitoring tracks positions, profit and loss, and exposures against limits. Post-trade controls confirm, match, and reconcile every transaction. No single control should be relied upon alone, and a control that is switched off for convenience is a control failure.

Segregation of duties is the central fraud control. The person who initiates a trade should not approve it, confirm it, release the related payment, or reconcile the account. Where staffing is small, compensating controls such as independent review by a manager, system-enforced maker-checker approval, and periodic reporting to a supervisor must be documented and tested.

• Mandatory: maker and checker must be different individuals for payments, static data changes, and limit changes.
• Mandatory: trade cancellations, amendments, and late bookings after market close need a reason code and second-person approval.
• Mandatory: personal trading must not take advantage of client orders or firm research, and must follow pre-clearance and holding-period rules where the firm applies them.
• Mandatory: positions must be reconciled daily to internal books, custodian records, and clearing records, with breaks investigated and aged under policy.
• Mandatory: margin and collateral calls must be met by the deadlines in the applicable agreement and clearing rules. A missed call is escalated immediately.
• Mandatory: valuations of hard-to-value instruments must be independently verified by someone outside the front office.
• Recommended: require consecutive block leave for traders and rotate reconciliation and approval duties to reveal concealed errors.

5Information, Data Confidentiality, and Technology Safeguards

Information is a core asset. Client data, order flow, pending transactions, positions, research, and material non-public information must be shared only on a need-to-know basis. Employees who hold such information may have legal duties, and the firm should maintain restricted and watch lists under its compliance procedures. Privacy and data protection rules are jurisdiction-dependent and should be verified with qualified privacy and legal professionals.

Technology safeguards include named user accounts, multifactor authentication, role-based access, session timeouts, and logging of all order, configuration, and permission changes. Credentials must never be shared. Trading systems change only through a documented change process with testing, approval, and rollback plans. Voice and electronic communications may need to be recorded and retained in some jurisdictions, so business communication should use approved channels only.

• Mandatory: do not use personal messaging apps or personal email for trade instructions or client matters unless the firm has approved and archived them.
• Mandatory: lock screens when leaving a workstation and keep order books and client files out of view of visitors. Visitors must be escorted.
• Mandatory: report lost devices, suspected phishing, or unusual system behavior to information security the same working day.
• Mandatory: model and algorithm changes require change approval, test evidence, and sign-off before production use.
• Recommended: run access reviews each quarter and remove access promptly when staff change roles or leave.

6Incident Reporting, Escalation, and Emergency Response

An incident is any event that causes or could cause financial loss, client harm, regulatory breach, or data exposure. Near misses, such as a mis-keyed order stopped by a limit check, must be reported because they reveal control weaknesses. Report immediately with the facts you have. Do not wait for a complete picture, do not fix the problem silently, and do not cover an error with an offsetting trade unless a supervisor has authorized it in writing.

Suspicious activity includes possible insider trading, front running, spoofing, layering, wash trades, unexplained cancellations, requests to bypass controls, and pressure to change a valuation. Escalate it to compliance and surveillance. Do not tip off the individuals involved or discuss the concern outside the escalation chain. Where a legal duty to report to a regulator applies, compliance decides the route and timing under jurisdiction-dependent requirements that counsel should confirm.

For a system outage, a runaway algorithm, or a suspected cyber intrusion, the named incident lead activates the kill switch or disconnection procedure, notifies the head of trading and the risk function, and follows the business continuity plan. Physical emergencies such as fire or medical events follow building procedures and involve emergency services. Staff must leave the trading floor when instructed and must not stay at workstations during an evacuation.

• Mandatory: report a suspected error or breach to the supervisor and operational risk immediately, including time, instrument, quantity, and systems involved.
• Mandatory: if a supervisor cannot be reached, escalate to the compliance duty officer.
• Mandatory: record every incident in the incident log with root cause, financial impact, and the named owner of each corrective action.
• Recommended: run tabletop exercises for runaway algorithm, failed settlement, and data breach scenarios at least annually.

7Records, Training, Inspection, and Review

Accurate books and records underpin safe practice. Orders, executions, amendments, confirmations, allocations, valuations, collateral movements, and relevant communications must be complete, time-stamped, and unaltered. Records should not be edited after the fact. Corrections are made by a documented adjustment showing the reason, the approver, and the original entry. Retention periods are jurisdiction-dependent and must be confirmed with compliance.

Training must be role-based and completed before access is granted, then refreshed on a schedule set by compliance. Topics include market conduct, insider information handling, conflicts of interest, cybersecurity, and escalation. Monitoring includes surveillance reviews, control testing, key risk indicator dashboards, and internal audit. Findings should produce owned corrective actions with due dates and closure evidence.

• Mandatory: keep attendance and attestation records for training and policy acknowledgments.
• Recommended: track key risk indicators such as aged reconciliation breaks, limit excess counts, and cancelled trade rates.
• Recommended: review these norms after any significant incident, system change, new product launch, or regulatory update.
• Mandatory: treat this document as a starting point. Replace or supplement it with locally approved procedures reviewed by compliance and legal counsel.

Implementation checklist

• Confirm written authorization and valid licensing before granting any trading or payment access.
• Enforce maker-checker separation for trades, payments, limit changes, and static data updates.
• Verify pre-trade price, size, and limit controls are active before each trading session starts.
• Reconcile positions, cash, and collateral daily, and age and escalate every open break.
• Use only approved, archived communication channels for trade instructions and client matters.
• Protect credentials and report phishing, lost devices, or odd system behavior the same working day.
• Escalate suspicious trading or pressure to bypass controls to compliance immediately, without tipping off.
• Record every incident and near miss with root cause, impact, and a named corrective action owner.
• Verify current laws, exchange rules, retention periods, and privacy duties with qualified professionals.
• Schedule review of these norms and related training after incidents, system changes, or product launches.