Chromebooks store browsing history locally in the Chrome browser profile. Over time this includes site URLs, search terms, and temporary files that can reveal your activity to anyone with physical access to the device. Deleting this data regularly also frees up a small amount of storage space and can resolve occasional loading issues caused by corrupted cache files.
Before starting, make sure your Chromebook is connected to Wi-Fi and updated to the latest Chrome OS version through Settings > About Chrome OS. No additional apps or extensions are required.
Click the circular account icon in the bottom-right corner of the shelf or open the Launcher and select the Chrome icon. Once Chrome launches, click the three vertical dots in the top-right corner, then select Settings from the dropdown menu.
In the left sidebar of Settings, click Privacy and security. Under this heading, select Clear browsing data. A new dialog box appears with multiple tabs and checkboxes.
At the top of the dialog, open the Time range dropdown and select All time to delete everything. Check the boxes for Browsing history, Cookies and other site data, and Cached images and files. Leave other options unchecked unless you specifically want to remove saved passwords or autofill data.
Click the blue Clear data button at the bottom of the dialog. Chrome immediately removes the selected information. You can verify success by returning to the History page (Ctrl+H) where no entries should remain.
No. The steps above only clear local data on the Chromebook. To delete synced history from your Google account, visit myactivity.google.com and remove items individually or in bulk.
Yes. Open Chrome, press Ctrl+H to view history, search for the site, hover over the entry, and click the three dots next to it to remove just that item.
Yes, if you also select Cookies and other site data. To stay signed in while removing history, uncheck that box before clicking Clear data.
Following these instructions makes it simple to delete history on Chromebook whenever you need to protect your privacy or free up space.
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.
