Choose your situation
A device is missing or data may have been exposed Protect university devices and files
Protect university devices and files
Protect files and devices, and report signs of malware or a lost device promptly.
Before you start
Use a trusted device and open university services from their official addresses. Never enter a password or code into this guide.
Actions for your situation
Preventive steps
- 1
Keep your operating system, browser and apps updated from trusted sources. Follow the responsible team's instructions on university-managed computers.
- 2
Lock your screen, do not leave devices unattended, and sign out on shared computers. Do not open unknown USB drives or files.
- 3
Store university files only in locations and with permissions approved by the responsible team. Check recipients and access before sharing.
- 4
Make backups of important files using an approved method and check that they can be restored. Do not use personal cloud accounts or drives for university data without approval.
Signs of malware or a lost device
- 5
If files suddenly cannot be opened, their names change unexpectedly, or a ransom demand appears, stop working with those files. If safe, disconnect the device from the network and promptly contact the IT Center. Do not wipe or reset it before receiving guidance.
- 6
If a device holding university data is lost or stolen, promptly notify the responsible unit and IT Center. Describe the device, approximate time and general type of data without sharing sensitive contents in a general report.
- 7
For suspected malware, note the time, device and warning message. Do not use the suspect device for sensitive sign-ins or send suspicious files, passwords or codes to others.
After these actions
If a device is lost or shows signs of malware, promptly notify the IT Center and responsible unit. This guide cannot confirm that a device or its data is safe.
Prepare a request draft; it is not submitted automatically
Sources and review status
Last text review: 3 October 2026
Editorial responsibility: Supplementary guide editorial team · University technical approval: not received; technical owner not designated
Next planned review: 2 November 2026
NIST cybersecurity basics ↗ · CISA guidance on protecting data stored on devices ↗ · IT Center service directory ↗
A university source link does not establish that all settings and policies are current.
Use your browser’s Print option to print or save a PDF. To share, copy this page’s address.
Secure network access or a suspicious connection warning Secure network access at the University of Ilam
Secure network access at the University of Ilam
Check the network, respond to certificate warnings, and report suspicious activity.
Before you start
Use a trusted device and open university services from their official addresses. Never enter a password or code into this guide.
Actions for your situation
Before connecting
- 1
Check the network name and sign-in method against the official university guide. A similar name alone does not prove authenticity.
- 2
Get Wi-Fi settings, certificates and connection software only from the IT Center. Never disable certificate validation to clear an error.
- 3
Check the full sign-in address. Do not enter passwords or security codes on unverified pages or share personal certificate files.
- 4
Use only the university-approved VPN for off-campus access if eligible. A VPN alone cannot verify a sign-in page or device safety.
- 5
Update and lock the device. Sign out of accounts and VPN on shared computers and disable unneeded file sharing.
I saw a suspicious network or warning
- 6
If you joined an unfamiliar network or saw a certificate warning, disconnect and note the name, time, location, device and error.
- 7
If you entered a password or code on a suspicious page, change the password using the official portal on a trusted device and promptly report it.
- 8
Report only non-sensitive details. A dedicated university network incident address has not been verified.
After these actions
If a network or certificate warning remains suspicious, disconnect and contact the IT Center. This guide cannot certify the network as safe.
Prepare a request draft; it is not submitted automatically
Sources and review status
Last text review: 3 October 2026
Editorial responsibility: Supplementary guide editorial team · University technical approval: not received; technical owner not designated
Next planned review: 2 November 2026
Campus wireless guide (Legacy source; a working original address has not been verified) · IT Center service directory ↗ · CISA guidance on public Wi-Fi safety ↗
A university source link does not establish that all settings and policies are current.
Use your browser’s Print option to print or save a PDF. To share, copy this page’s address.
I received a suspicious message or link Phishing: recognize a fake message and respond
Phishing: recognize a fake message and respond
Recognize suspicious messages and choose what to do based on whether you opened a link, ran a file, or shared information.
Before you start
Use a trusted device and open university services from their official addresses. Never enter a password or code into this guide.
Actions for your situation
I received a message
- 1
If you only received a message, treat urgent account threats, requests for passwords or codes, unexpected attachments, and lookalike domains as reasons to check further. These signs alone do not prove phishing.
- 2
Do not open suspicious links or attachments or reply. Visit the university service from an official source you open yourself, or check the message through an official IT Center contact.
- 3
Check the full address before signing in. The university identity portal uses auth.ilam.ac.ir. A padlock or HTTPS alone cannot establish that a lookalike domain is genuine.
I opened a link or downloaded or ran a file
- 4
If you opened a link but entered nothing, close the page and do not download or run anything. Note the time, address and message for a report. Opening a link alone does not establish that your password was stolen.
- 5
If you only downloaded an unknown file, do not open or run it; ask the IT Center how to remove it safely. If you opened or ran it, avoid sensitive sign-ins on that device and promptly ask the IT Center to assess it. Report any signs of infection or unexpected installation prompts.
I entered or shared credentials
- 6
If you entered a password or code, open the official portal yourself on a trusted device and change your password. Do not approve an unexpected sign-in request; ask the IT Center to check your sign-in methods and active sessions.
- 7
If you exposed recovery codes, an authenticator QR code or a personal certificate file, say so in the report so those access methods can be reviewed and replaced if necessary.
Report the incident
- 8
Report promptly through the university's official support route with the time, sender, suspicious address and action taken. Never send passwords, current codes, QR codes or certificate files. A dedicated phishing address has not been verified.
After these actions
The next step depends on what you did. Changing a password alone does not complete incident response if a file ran or an access method was exposed. Contact the IT Center.
Prepare a request draft; it is not submitted automatically
Sources and review status
Last text review: 3 October 2026
Editorial responsibility: Supplementary guide editorial team · University technical approval: not received; technical owner not designated
Next planned review: 2 November 2026
Account and authentication guide ↗ · CISA guidance on recognizing and responding to phishing ↗
A university source link does not establish that all settings and policies are current.
Use your browser’s Print option to print or save a PDF. To share, copy this page’s address.
My account may be accessed or my password exposed First steps if your password may be exposed
First steps if your password may be exposed
Choose the appropriate recovery path if a password was exposed or you lost access to your account.
Before you start
Use a trusted device and open university services from their official addresses. Never enter a password or code into this guide.
Open the official sign-in and recovery portal ↗
Actions for your situation
I can still sign in
- 1
If you can still sign in and your password may have been exposed, open the official university identity portal yourself on a trusted device and change it. Change the password on other accounts where you reused it, using a unique password for each.
I cannot sign in
- 2
If you cannot sign in, check the password recovery option on the official university identity portal and contact the IT Center for help. Do not use a recovery link from a suspicious message.
Review access and report
- 3
If available, sign out of active sessions and review your two-factor sign-in methods and recovery details. Ask the IT Center for help if these options are unavailable or you find unfamiliar changes.
- 4
Report the time and signs of possible exposure through the IT Center's published general contact. Ask for referral if needed. Never send passwords, current or recovery codes, authenticator QR codes or certificate files.
After these actions
Whether you changed the password or started account recovery, review sign-in methods and sessions if available and report the possible exposure. This guide cannot confirm that unauthorized access has ended.
Prepare a request draft; it is not submitted automatically
Sources and review status
Last text review: 3 October 2026
Editorial responsibility: Supplementary guide editorial team · University technical approval: not received; technical owner not designated
Next planned review: 2 November 2026
Account and authentication guide ↗ · Official university identity sign-in and recovery portal ↗ · NCSC guidance on recovering a compromised account ↗ · IT Center service directory ↗
A university source link does not establish that all settings and policies are current.
Use your browser’s Print option to print or save a PDF. To share, copy this page’s address.
The university's dedicated security incident channel and approval of these instructions have not been confirmed.
More questions about this service
