The online learning application Zoom is becoming a phenomenon that teachers use to teach online. Not only that, businesses also consider Zoom as a convenient online meeting tool, bringing high efficiency because of its simple and easy-to-use usage.
However, Zoom is also leaving a lot of worries related to the security of users' personal information. Many organizations recommend data safety when using Zoom for online meetings. So how to ensure information security when using Zoom for online learning and online meetings for users' Zoom accounts? Below is how to secure information when studying online on Zoom.
Security instructions when teaching online on Zoom
Please regularly update the new version of Zoom to fix security-related errors. The Zoom download link below is always updated to the latest so you can download and install it for your device.
Or click on the Zoom account avatar and select Check for Updates to update to the new version.
Update new version Zoom
Administrators who create classrooms and meeting rooms sometimes skip the step of creating a password for the classroom, causing the classrooms to be infiltrated by bad actors. Therefore, every online meeting or distance learning needs to set up a password to require participants to enter an access password.
Create a classroom password
The Waiting room feature in Zoom is responsible for reviewing people who want to participate in the online class you have created.
Click Schedule meeting and select Advanced Options and check Enable waiting room.
Approve participation in class on Zoom
In the online learning interface, if you are the Host, you can control screen sharing by clicking Share Screen and then clicking Advanced Sharing Options...
Manage Zoom screen sharing
If you're on a computer call, use your phone to check email or text with other people on the call.
Signing in with a Facebook account will save time but has poor security and significantly increases the risk of the amount of personal data that Zoom can access.
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.
