How Core iQ Users Should Report a Security Breach or Potential Breach

If you use Core iQ and discover a security breach or a potential security breach affecting your institution, report it immediately by email to [email protected]. This is the contact route published on onovativebanking.com, which now operates as a resource hub for Core iQ clients under Main Street, Inc. The instruction applies to both confirmed breaches and suspected ones — the site does not ask you to wait for confirmation before notifying.

What Counts as a Reportable Incident

The page frames the trigger broadly: "a security breach or potential security breach affecting your institution." In practice, that covers situations such as:

• Unauthorized access to a Core iQ account or administrative credentials
• Suspicious login activity, password changes, or permission changes you did not initiate
• Exposure of client or institution data through the platform or connected systems
• Lost or compromised devices used to access Core iQ
• Any event where you suspect data or access may have been compromised, even without proof

If you are unsure whether an event qualifies, treat it as potential and report it. The published guidance does not set a threshold below which notification can be skipped.

How to Send the Report

1. Compose an email to [email protected] from an address your institution monitors.
2. State clearly in the subject line that this is a security incident report so it is routed correctly.
3. Describe what happened — what you observed, when you noticed it, and which systems or accounts appear affected.
4. Include your institution name and a direct contact so the team can follow up with questions.
5. Send immediately rather than waiting to complete a full investigation; additional details can follow in later messages.

Expected result: your report reaches the Main Street security contact, and you have a written record of the notification with a timestamp.

What to Do While You Wait for a Response

The site does not publish a response-time commitment or an incident-handling playbook, so plan around that gap:

• Preserve evidence — keep relevant logs, screenshots, and email headers rather than deleting or overwriting them.
• Avoid independent public disclosure or broad internal circulation until you have coordinated with the security contact.
• Continue using the standard support channel for ordinary product issues, but keep security matters on the dedicated email address above.

Related Support Paths on the Same Site

The hub separates security reporting from routine help, so use the right channel:

Mixing a security report into a general support ticket risks delay, so send it to the security address first and use support for everything else.

Context Worth Knowing

Core iQ remains fully operational as part of Main Street, and the site states there are no major changes or anticipated disruptions to the user experience. That matters for reporting: the security contact is current, and you do not need to route breach notifications through a legacy Onovative address. If your institution is also evaluating Connect by Main Street, note that the site describes it as core-integrated and SOC 2 compliant — but the breach-reporting instruction above applies to Core iQ users regardless of migration status.