Confidential, Internal Use
Information Security Policy and Operational Security Program
Black Americanway, Inc. · Black Americanway Cash Card Program
- Organization
- Black Americanway, Inc.
- Program
- Black Americanway Cash Card Program
- Location
- Tulsa, Oklahoma
- Responsible Executive
- Marion Avance, President/Founder
- Technology
- Black Americanway website and application, Plaid API, and future card issuing and processing partner
- Version
- Version 1.0
- Effective
- Effective upon approval
Purpose
This Information Security Policy and Operational Security Program establishes the minimum controls, responsibilities, and operating practices Black Americanway, Inc. uses to protect the confidential, customer, financial, authentication, and technology information entrusted to it through the Black Americanway Cash Card Program.
The program is designed to preserve the confidentiality, integrity, and availability of member information, to support the safe operation of member-to-member transfers and card funding, and to demonstrate a defensible, documented security posture to members, banking and issuing partners, payment processors, and regulators.
This policy applies in addition to, and never in place of, contractual security obligations owed to third parties, including the requirements of the card issuing and processing partner and the obligations that accompany use of the Plaid API.
Scope and Applicability
This policy applies to:
- All employees, officers, contractors, temporary staff, and interns of Black Americanway, Inc.
- All systems supporting the Cash Card Program, including the public website, the authenticated member application, server functions, databases, file storage, and administrative tooling.
- All data the organization creates, receives, stores, transmits, or processes in support of the program, including member identity data, balances, transaction records, funding records, and payment request records.
- All third-party services connected to the program, including the Plaid API and any future card issuing, card processing, or payment facilitation partner.
Where a third party processes information on the organization's behalf, responsibility for compliance with this policy remains with Black Americanway, Inc. and is managed through vendor risk management as described in Section 11.
Governance and Responsibilities
Ultimate accountability for information security rests with the President/Founder, who serves as the Responsible Executive for this program and approves this policy, material changes to it, and acceptance of significant residual risk.
| Role | Security Responsibilities |
|---|---|
| President/Founder (Responsible Executive) | Approves policy and risk decisions; allocates resources; receives incident and program status reporting; serves as the primary contact for banking, issuing, and processing partners. |
| Information Security Officer (designated) | Owns the program day to day; maintains this policy and supporting procedures; coordinates risk assessments, vendor reviews, access reviews, and incident response; reports material matters to the Responsible Executive. |
| Engineering and Operations | Builds and maintains systems according to Section 12; enforces access control, encryption, logging, and change management requirements; remediates vulnerabilities and responds to incidents. |
| All Personnel | Follow this policy and related procedures; protect credentials and devices; report suspected incidents or policy violations promptly; complete required training. |
| Third-Party Providers | Meet contractual and regulatory security obligations; notify Black Americanway of incidents affecting program data; cooperate with investigations and reviews. |
Where the organization is small, one individual may hold more than one role. Conflicting duties affecting money movement, such as initiating and approving a balance adjustment, are separated wherever practical and are documented when not.
Regulatory and Framework Alignment
The program is mapped to the following authorities and recognized frameworks, proportionate to the organization's size and risk profile:
- Gramm-Leach-Bliley Act and the FTC Safeguards Rule, including designation of a qualified individual, written risk assessment, access controls, encryption, vendor oversight, and incident response.
- Payment Card Industry Data Security Standard (PCI DSS), through scope reduction and, where applicable, Self-Assessment Questionnaire completion with the issuing or processing partner.
- Consumer Financial Protection Bureau Regulation E principles for error resolution and provisional credit on member disputes.
- Bank Secrecy Act and anti-money-laundering expectations as flowed down by the issuing or banking partner, including customer identification and transaction monitoring cooperation.
- Oklahoma breach notification law (24 O.S. Section 163) and applicable state privacy and data disposal requirements.
- NIST Cybersecurity Framework and ISO/IEC 27001 as reference control catalogs for structuring and evaluating the program.
Alignment statements describe intent and control design. Certification against any framework is claimed only where an independent assessment has been completed and documented.
Information Classification and Handling
All information is classified at creation or receipt and handled according to its classification. Classification drives access, encryption, retention, and sharing decisions.
| Classification | Examples | Handling Requirements |
|---|---|---|
| Restricted | Authentication secrets, API and access tokens, bank account identifiers, full card data, government identifiers, credentials, encryption keys. | Encrypted at rest and in transit; least-privilege access; no transmission by ordinary email or chat; no storage on personal devices; access logged. |
| Confidential | Member names, email addresses, balances, transaction and request history, vendor contracts, security documentation. | Access limited to personnel with a business need; encrypted in transit; shared only through approved channels. |
| Internal | Operating procedures, internal reporting, project plans, non-public business metrics. | Available to personnel and contractors; not distributed externally without approval. |
| Public | Published policies, marketing content, terms of service, public support information. | No handling restrictions; approved before publication. |
Data is retained only as long as required for operational, contractual, tax, and regulatory purposes, then disposed of through approved deletion methods. Records tied to money movement are retained for the period required by the issuing or banking partner and applicable law.
Access Control and Identity Management
Access to program systems and data is granted on a least-privilege, need-to-know basis, is approved before it is provisioned, and is removed promptly when no longer required.
- Every user of an administrative or internal system has a unique identity. Shared accounts are prohibited except where a platform technically requires one, in which case the credential is vaulted and its use is logged.
- Multi-factor authentication is required for all administrative, engineering, cloud, source control, email, and payment platform access.
- Privileged access is limited to a named, documented group, is reviewed at least quarterly, and is removed within one business day of a role change or separation.
- Passwords meet current length and complexity guidance, are never reused across services, and are stored only in an approved password manager.
- Role-based access is enforced in the application and in database access rules, so that members can read only their own wallets, transactions, and requests.
- Access reviews are performed at least quarterly and after any material staffing change, and the results are retained as evidence.
- Accounts dormant for an extended period are disabled, and vendor or contractor access expires automatically at the end of the engagement.
Customer Authentication and Account Protection
Member accounts are protected by layered authentication and continuous monitoring proportionate to the sensitivity of money movement.
- Registration verifies email ownership through a one-time code before an account becomes usable.
- Multi-factor authentication is available to members and is required for administrative accounts.
- Sessions use platform-issued tokens, are invalidated on sign-out, and expire after a defined idle period. Tokens are never placed in URLs or logs.
- Authentication failures are rate limited and monitored; repeated failures trigger additional verification or temporary lockout.
- Password reset flows use single-use, time-limited tokens and never disclose whether an address is registered.
- Sensitive account changes, such as adding a new funding source or changing contact details, are confirmed through the registered channel.
- Money movement is validated server-side against the authenticated member, available balance, and the recipient's existence, and client-supplied amounts or identities are never trusted.
Suspected account takeover, unauthorized transfer, or identity fraud is handled as a security incident under Section 15 and, where applicable, as an error resolution matter under Regulation E.
Data Protection, Encryption, and Key Management
- All traffic between members, browsers, and program services is encrypted using TLS 1.2 or higher; insecure protocols and legacy ciphers are disabled.
- Restricted and Confidential data is encrypted at rest using provider-managed encryption, with application-level protection for secrets and tokens.
- API keys, signing secrets, and access tokens are stored in the platform's secret manager and injected into server-side code at runtime. Secrets are never committed to source control, embedded in client bundles, or exposed to the browser.
- Encryption keys and secrets are rotated on a defined schedule, on suspicion of compromise, and when a custodian leaves the organization.
- Production data is not copied into development or test environments. Where realistic data is required, it is synthesized or de-identified.
- Files uploaded by members are stored privately and served only through short-lived signed links, and never in publicly readable storage.
- Backups are encrypted, access-restricted, and tested for restoration at least annually.
Plaid API Integration Security
Plaid is used to verify member bank accounts and to support funding and payout flows. Integration with Plaid follows Plaid's security requirements and the organization's own least-privilege standard.
- Plaid client identifiers and secrets are stored server-side only and are never exposed to the browser or mobile client.
- Link tokens are short-lived, created server-side for a single use, and are never logged or retained after the session completes.
- Plaid access tokens are stored encrypted, are scoped to the minimum products and accounts needed, and are never displayed in any user interface.
- Bank credentials entered by members are handled by Plaid's Link interface. Black Americanway never requests, receives, or stores member online banking usernames or passwords.
- Webhooks and callbacks from Plaid are authenticated by verifying the declared webhook signature or a shared secret before any state change is made.
- Access tokens are revoked through Plaid when a member closes an account or when a connection is no longer required.
- Sandbox and development credentials are kept separate from production credentials, and production access is granted to the fewest possible systems.
- Changes to Plaid products, scopes, or integrations are reviewed and approved through change management before deployment.
Card Issuing and Processing Partner Security
Card issuance and processing are performed by a licensed partner. Black Americanway is designed to remain out of scope for storing card numbers wherever possible, and this section sets expectations for that relationship as it is established.
- The issuing and processing partner must maintain PCI DSS compliance, provide evidence of compliance at least annually, and notify Black Americanway of any change in compliance status.
- Card numbers, CVV values, magnetic stripe data, and PIN data are never stored in Black Americanway systems. Where a card identifier is displayed, only the last four digits are retained.
- Card data captured through any interface is tokenized by the processor, and tokens, not card numbers, are used for subsequent operations.
- Partner APIs are authenticated with scoped credentials held server-side, transmitted over TLS, and rotated on a defined schedule.
- Dispute, chargeback, and fraud workflows are documented with the partner, including member contact points, response timelines, and evidence retention.
- A written agreement addressing confidentiality, data use, incident notification, audit rights, subcontracting, and data return or destruction is executed before launch.
Vendor and Third-Party Risk Management
Third parties that can affect program data or money movement are assessed before engagement, monitored during the relationship, and reviewed at least annually.
- 1.Inventory every vendor that stores, processes, or transmits program data, and record the data categories and access each requires.
- 2.Perform risk-based due diligence: security documentation, independent attestations where available, breach history, encryption and access practices, and financial viability.
- 3.Execute contracts that require confidentiality, security safeguards, breach notification without undue delay, cooperation with investigations, and defined data return or destruction.
- 4.Restrict vendor access to the minimum data and systems needed, with named accounts and no standing production access where avoidable.
- 5.Review vendor security posture, incidents, and certification currency at least annually, and after any material change in services.
- 6.Maintain an exit plan for critical vendors, including data retrieval and transition of member-facing functions.
Secure Development and Change Management
- All changes to production code, configuration, access rules, or infrastructure are reviewed by a second person before deployment and are traceable to a documented request.
- Source code is held in version control with branch protection; direct pushes to production branches are restricted.
- Server-side code enforces authentication, authorization, input validation, and rate limits for every operation that moves money or reads member data. Client-side checks are treated as convenience only.
- Database access rules restrict each member to their own records and reserve privileged writes for administrators.
- Secrets and credentials are supplied through the secret manager, and automated checks prevent secrets from entering source control.
- Dependencies are pinned, reviewed before adoption, and monitored for known vulnerabilities.
- Rollback procedures exist for each release, and releases that affect money movement are verified in a non-production environment first.
- Production data is never used in test environments without de-identification.
Vulnerability Management and Configuration Standards
- Systems are configured from documented baselines: minimal services, current software versions, least-privilege service accounts, and disabled default accounts.
- Dependency and platform vulnerability alerts are reviewed continuously and remediated on a risk basis: critical findings within 7 days, high within 30 days, medium within 90 days, with documented exceptions where remediation is not feasible.
- Application security testing, including dependency scanning and targeted review of authentication and money-movement paths, is performed before major releases and at least annually.
- An independent penetration test of member-facing systems is obtained at least annually and before major architectural change; findings are tracked to closure.
- Cloud and platform configuration is reviewed at least annually against the principle of least privilege and against public exposure of storage, endpoints, and administrative interfaces.
- Logging and monitoring are enabled before a system is exposed to the internet, not added after launch.
Logging, Monitoring, and Detection
- Authentication events, administrative actions, access-rule changes, money movement, funding events, and configuration changes are logged with actor, timestamp, source, and outcome.
- Logs exclude secrets, tokens, full card data, and unnecessary personal data, and are protected from modification by the systems that generate them.
- Security-relevant logs are retained for at least twelve months, with at least three months readily searchable, unless a partner or legal requirement specifies longer.
- Automated alerts cover repeated authentication failures, unusual transfer velocity or amounts, administrative privilege changes, and errors in payment processing.
- Suspicious activity is triaged, documented, and, where warranted, escalated under Section 15.
- Access to logs is limited to personnel with an operational need, and log access itself is logged.
Incident Response and Breach Notification
A security incident is any actual or suspected event that threatens the confidentiality, integrity, or availability of program data or systems, including unauthorized access, account takeover, fraudulent transfers, lost devices, and vendor-reported breaches.
| Phase | Activities |
|---|---|
| Prepare | Maintain this policy, contact lists, evidence templates, and vendor escalation paths; train personnel; test the plan at least annually. |
| Identify | Receive reports through any channel, log the incident, assign an owner, and classify severity. |
| Contain | Disable affected accounts, revoke tokens, rotate secrets, isolate systems, and preserve evidence before remediation. |
| Eradicate and Recover | Remove the cause, restore service from trusted state, verify integrity, and monitor for recurrence. |
| Notify | Notify the Responsible Executive, affected members, the issuing or banking partner, Plaid where their systems are implicated, and regulators or law enforcement as required. |
| Learn | Complete a written post-incident review within 30 days, assign corrective actions, and track them to closure. |
Regulatory and contractual notification timelines are followed where they are stricter than internal targets. Oklahoma law requires notification of affected individuals without unreasonable delay, and partner agreements may require notice within 24 to 72 hours. Notification content is reviewed by the Responsible Executive before release.
Members can report suspected fraud or account compromise through the support channel published on the website. Reports are acknowledged promptly and handled under this section and, for unauthorized transfers, under the organization's Regulation E error resolution procedure.
Business Continuity and Disaster Recovery
- Recovery objectives are defined for member-facing services: a recovery time objective of 24 hours and a recovery point objective of 24 hours for core account and transaction data, with tighter targets for payment processing where the partner requires it.
- Backups of databases and configuration are taken automatically, encrypted, and stored in a separate location from production.
- Restoration from backup is tested at least annually and after material architecture changes, with results documented.
- Critical dependencies, including Plaid and the card issuing and processing partner, have documented fallback or manual procedures for outages.
- A business impact analysis is reviewed annually to confirm that priorities and recovery targets remain accurate.
- Continuity and recovery procedures are exercised at least annually, and gaps are tracked to closure.
Personnel Security and Awareness Training
- Background checks are performed for personnel with access to Restricted or Confidential data, to the extent permitted by law.
- All personnel complete security awareness training at onboarding and at least annually, covering phishing, credential handling, secure handling of member data, social engineering, and incident reporting.
- Confidentiality agreements are executed at hire and acknowledged again on separation.
- Access is revoked and devices and credentials are recovered on the final day of employment or engagement, with a documented checklist.
- Personnel report suspected phishing, lost devices, and policy violations promptly, without fear of reprisal for good-faith reporting.
- Targeted role-based training is provided to engineering and administrative personnel on secure development, secrets management, and payment operations.
Physical and Remote Work Security
- Program data is stored in cloud services, not in physical filing systems. Any physical media containing Confidential data is inventoried, secured, and destroyed when no longer needed.
- Workstations require screen lock after a short idle period, full-disk encryption, current operating system patches, endpoint protection, and automatic updates.
- Remote access to administrative systems requires multi-factor authentication over an encrypted connection.
- Member data is not discussed or displayed where it can be observed by unauthorized persons, and is not printed unless necessary.
- Lost or stolen devices are reported immediately so that sessions and credentials can be revoked.
- Personnel do not use personal email or consumer file-sharing services for program data.
Risk Assessment, Audit, and Program Review
- A written risk assessment is performed at least annually and before launching a new product, integrating a new vendor, or making a material change to money movement.
- The assessment identifies threats and vulnerabilities, evaluates likelihood and impact, records existing controls, and assigns owners and due dates to treatment plans.
- Residual risk above the organization's defined tolerance is accepted in writing by the Responsible Executive.
- This policy and its supporting procedures are reviewed at least annually and after any material incident, regulatory change, or partner requirement.
- Program effectiveness is measured with a small set of indicators, including open critical findings, access review completion, training completion, incident volumes, and vendor review currency, reported to the Responsible Executive at least annually.
- Records supporting the program, including risk assessments, access reviews, training records, vendor reviews, test results, and incident reports, are retained for at least three years or as required by partners and law.
Exceptions, Enforcement, and Review
Exceptions to this policy require a written request describing the requirement, the business justification, the compensating controls, and a proposed expiration date. Exceptions are approved by the Responsible Executive, recorded in a register, and reviewed at least annually.
Violations of this policy may result in corrective action, up to and including termination of employment or contract, and may be referred to law enforcement where appropriate. Suspected violations are investigated by the Information Security Officer and reported to the Responsible Executive.
This policy takes effect on approval and remains in force until replaced. It is reviewed at least annually, and the current approved version is retained with the approval record in Appendix A.
Appendix A
Approval and Certification
Management Approval
Black Americanway, Inc. adopts this Information Security Policy as the governing framework for protecting confidential, customer, financial, authentication, and technology information associated with the Black Americanway Cash Card Program.
- Approved by:
- Marion Avance
- Title:
- President/Founder
- Organization:
- Black Americanway, Inc.
- Date:
- ______________________
- Signature:
This approval record is retained with the current version of the policy. Any material amendment requires a new signed approval page and a new version number.