Before you begin

  • Access to the Encrisoft website: You should be able to access the website and its customer support chat widget.
  • Details of the security concern: Have relevant information ready, including what happened, when you noticed it, and any affected account or activity.
  • Prepare relevant screenshots, suspicious email details, or notifications that may help explain the issue. Ensure you do not expose passwords or other sensitive authentication information.

Introduction

A suspicious email lands in your inbox. You notice a sign-in notification you don't recognise. Perhaps something about an account change doesn't look right. You might be looking at a genuine security threat, or there may be a harmless explanation. The important thing is not to ignore it simply because you're unsure. Reporting a security concern gives the appropriate team an opportunity to assess what happened and determine whether action is needed. You don't have to prove that an incident has occurred before raising a concern. You need to communicate what you've noticed clearly and promptly.

Encrisoft helps organisations strengthen security awareness through phishing simulations, security training, and human cyber risk insights. Recognising and reporting suspicious activity complements these efforts by helping organisations respond more effectively to potential threats.

This article explains how to identify a security concern, prepare a useful report, and take appropriate next steps.

Security concerns can take different forms, from suspicious messages and unfamiliar account activity to the potential exposure of sensitive information.

What Should You Report?

Not every unusual event is a security incident, but certain situations deserve closer attention.

You should consider reporting activity such as:

  • Suspicious emails or messages: Communications that ask you to reveal sensitive information, click unexpected links, open questionable attachments, or take urgent action without a clear reason.
  • Unrecognised account activity: Sign-in notifications, account changes, or other activity you did not initiate or approve.
  • Possible unauthorised access: Signs that someone may have accessed an account, system, or organisational information without permission.
  • Unexpected requests for sensitive information: Requests for passwords, authentication codes, confidential documents, or information that should not be shared.
  • Potential data exposure: Situations in which confidential information may have reached someone who should not have access to it.
  • Suspicious activity involving Encrisoft: Unexpected account behaviour or other activity involving the platform that may indicate a security issue.

If you're uncertain whether an event qualifies as a security concern, focus on what you observed and report it through the appropriate channel. The responsible team can assess the details and determine whether further investigation is necessary.

How to Report a Security Concern

Once you've identified something suspicious, the next step is to communicate it clearly. The following process will help you prepare a useful report without exposing additional information or putting yourself at unnecessary risk.

Step 1: Identify What Happened

Start by describing the activity that raised your concern. Did you receive an unexpected email? Notice a sign-in you couldn't account for? Discover an unfamiliar change to an account? Be specific about what you observed and why it concerns you. For example, instead of writing that an email looked suspicious, explain that it requested your password and claimed your account would be disabled unless you responded immediately. You don't need to determine exactly how an attack works or identify who may be responsible. Your role is to communicate the warning signs you've noticed. If the concern involves a suspicious message, avoid clicking its links, opening unexpected attachments, or replying to the sender.

Security concerns can take different forms, from suspicious messages and unfamiliar account activity to the potential exposure of sensitive information.

Step 2: Gather the Relevant Details

A useful report gives the receiving team enough information to understand the situation and decide what to investigate.

Where available, include:

  • Description: What happened, what you observed, and why you believe it may present a security risk.
  • Date and time: When you first noticed the activity. Include the time zone if it may be relevant.
  • Affected account or resource: Identify the account, system, device, or organisational resource involved.
  • Supporting evidence: Provide relevant screenshots, message details, notifications, or error messages where appropriate.
  • Actions already taken: Explain whether you clicked a link, opened an attachment, entered information, or noticed any subsequent activity.
  • Potential impact: Indicate whether an account, device, system, or organisational information may be affected.

You may not have all these details, and that's fine. Include what you know rather than delaying an urgent report while trying to collect every piece of information. Protect sensitive information. Never include passwords, one-time authentication codes, recovery codes, or other authentication secrets in your report. If evidence contains confidential information, use your organisation's approved method for sharing it.

Step 3: Contact Encrisoft Support

Once you've gathered the relevant information, you're ready to contact Encrisoft Support. You can reach the customer support team through the chat widget on the Encrisoft website or by sending an email to support@encrisoft.com.

Option 1: Use the Website Chat

Visit the Encrisoft website and locate the chat icon in the bottom-right corner of the page. Select the icon to open the chat panel, then follow the available prompts to contact the customer support team. Explain your concern clearly, including what happened, when you noticed it, and any account or activity that may be affected. Provide relevant details or supporting evidence to help the team understand the issue and determine the appropriate next steps.

The chat icon in the bottom-right corner of the Encrisoft website is the starting point for contacting Support.

Option 2: Send an Email

Alternatively, you can email support@encrisoft.com to report your concern. Use a clear subject line, such as Security Concern: Suspicious Account Activity, so the purpose of your message is immediately apparent. In the body of your email, describe what happened, when you noticed it, and why you believe it may present a security risk. Include relevant screenshots or other supporting evidence where appropriate, ensuring that you do not expose unnecessary confidential information.

Whichever method you choose, provide as much relevant detail as possible to help the support team understand your concern. Never include your password, one-time authentication codes, recovery codes, or other sensitive authentication details in your message. If you suspect an active security incident, such as unauthorised access to your account, notify your organisation's IT or security team immediately as well. Contacting Encrisoft Support addresses your platform-related concern, while your organisation's security team can coordinate the response to any wider security incident.

Step 4: Follow Up on Your Report

After submitting your report, follow any instructions provided by the Encrisoft Support team. They may need clarification about the issue or request additional information to help them assess your concern. Respond to relevant requests and provide any further details needed to clarify what happened. If the issue persists or you notice new suspicious activity, communicate the update through the same support conversation where possible. If you suspect that your account has been compromised or that you've disclosed sensitive credentials, follow your organisation's account-security procedures immediately. Do not wait for a response from customer support before taking the protective steps recommended by your organisation's IT or security team.

Step 5: Keep a Record of Your Report

Keep a record of your support conversation and any relevant instructions provided by the team. If you receive a case reference or confirmation, save it so you can easily refer to it if you need to follow up. Retaining these details helps you track the progress of your concern and provides a useful reference if the issue occurs again or further information is required.

What If You Suspect Your Account Has Been Compromised?

A suspected account compromise requires particular attention because an unauthorised person may be able to access information or perform actions using the affected account.

If you believe your Encrisoft account or another organisational account has been compromised:

  1. Report it promptly. Contact your organisation's designated security contact or follow its incident-response procedure.
  2. Secure the affected account. Follow your organisation's approved account-recovery and security instructions.
  3. Protect your credentials. Never send passwords, authentication codes, or recovery codes to someone claiming to investigate the incident.
  4. Preserve relevant evidence. Keep useful notifications, timestamps, and other relevant details where it is safe and appropriate to do so.
  5. Follow up. Provide any additional information requested by the team handling the incident.

If the incident appears to be ongoing, use the appropriate urgent reporting and escalation process. Do not wait for a routine support response before notifying the people responsible for your organisation's security.

Security Concern or Technical Support Issue?

Sometimes, a problem looks technical at first but may have security implications. Knowing the difference helps you direct your report to the right team.

A technical support issue typically involves a product or functionality problem. For example, a page may fail to load, an invitation may not work as expected, or a phishing simulation may fail to launch.

A security concern involves a possible threat to an account, system, or organisational information. Examples include suspicious sign-in activity, suspected unauthorised access, or the possible exposure of sensitive information.

Consider an example: an employee notices an unfamiliar change to an account. If the change resulted from an ordinary configuration error, it may be a technical issue. If the employee did not authorise the change and suspects someone else made it, the situation may also require a security investigation.

Some issues can fall into both categories. In those cases, report the security concern through the appropriate security channel and contact Encrisoft Support if the platform itself is involved.

When you're unsure, explain what happened rather than trying to classify the incident yourself. The appropriate team can assess the information and determine how the issue should be handled.

Best Practices for Reporting Security Concerns

A good security report doesn't need to be complicated. It needs to be clear, timely, and useful.

Keep these principles in mind:

  • Report promptly. Don't dismiss suspicious activity simply because you cannot confirm that a threat exists.
  • Describe what you observed. Include relevant details and distinguish confirmed facts from assumptions.
  • Preserve useful evidence. Retain relevant information where it is safe and appropriate to do so.
  • Protect confidential information. Never share passwords, authentication codes, or unnecessary sensitive data in a report.
  • Use the appropriate channel. Follow your organisation's reporting procedure and use official Encrisoft Support channels for platform-related issues.
  • Follow up when necessary. Respond to requests for additional information and report significant changes through the established process.

Security is everyone's responsibility, but recognising a potential threat is only half the job. What happens next matters just as much. A timely report can give the right people the opportunity to investigate, respond, and prevent a small concern from becoming a much bigger problem.

You don't need to have all the answers to raise a concern. You just need to know when something doesn't look right—and what to do about it.