Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Laptop Hardware Security #244

Draft
wants to merge 60 commits into
base: main
Choose a base branch
from
Draft

Laptop Hardware Security #244

wants to merge 60 commits into from

Conversation

TommyTran732
Copy link
Member

No description provided.

Copy link

cloudflare-workers-and-pages bot commented Jun 10, 2024

Deploying privsec-dev with  Cloudflare Pages  Cloudflare Pages

Latest commit: 6ff18d4
Status: ✅  Deploy successful!
Preview URL: https://4fa2b80c.privsec-dev-2oz.pages.dev
Branch Preview URL: https://laptop-hardware-security.privsec-dev-2oz.pages.dev

View logs

@TommyTran732 TommyTran732 marked this pull request as draft June 10, 2024 09:47
Copy link

netlify bot commented Jun 10, 2024

Deploy Preview for privsec-dev ready!

Name Link
🔨 Latest commit 6ff18d4
🔍 Latest deploy log https://app.netlify.com/sites/privsec-dev/deploys/666774f691f5d000086394b4
😎 Deploy Preview https://deploy-preview-244--privsec-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Copy link
Member

@wj25czxj47bu6q wj25czxj47bu6q left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Post images should not be placed in the /static directory. Follow the correct format as in https://github.com/PrivSec-dev/privsec.dev/tree/main/content/posts/knowledge/ChromeOS%20Questionable%20Encryption.

@TommyTran732
Copy link
Member Author

Are we gonna start moving other posts later too? Because there are a lot of them in /static

Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
Signed-off-by: Tommy <[email protected]>
To start off, the best laptops I have found are modern the Dell Latitude/Precision laptops with an Intel vPro Enterprise CPU. The second best group of laptops I have found are modern Lenovo Thinkpads with Intel vPro Enterprise or AMD Ryzen Pro CPUs. These are relatively easy to acquire and share these common security properties:

- Have Intel Boot Guard or AMD Platform Secure Boot to protect the firmware
- Have regular firmware updates ([monthly updates for Dell](https://www.dell.com/support/kbdoc/en-us/000197092/dell-drivers-and-downloads-update-release-schedule), and [bi-monthly updates for Thinkpads](https://support.lenovo.com/us/en/solutions/ht515365-thinkpad-driver-and-firmware-update-release-schedule))

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems it's not strictly one update per month. Sometimes there's several months without updates.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also Dell and Lenovo never promised how long they would support their PCs

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems it's not strictly one update per month. Sometimes there's several months without updates.

Yes, its a general rule. It doesn't always hold.

Also Dell and Lenovo never promised how long they would support their PCs

They typically support them for years and years. Even 8th gen Dell and Lenovo are still getting updates.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lenovo's Product Specification Reference does have an ‘End of Support’ column: https://psref.lenovo.com/Product/ThinkPad/ThinkPad_T14_Gen_5_Intel?tab=model.

@TommyTran732 TommyTran732 force-pushed the main branch 4 times, most recently from 520b835 to c508504 Compare July 8, 2024 03:52
@duck09
Copy link

duck09 commented Oct 11, 2024

Have the Microsoft Surface line of laptops been considered? Not the ARM ones (not sure if they they have memory encryption) but the Surface Laptop 6 for example. I'm pretty sure they meet all the requirements and the only downside would be Linux support but this is an article about general Laptop Hardware Security. Thoughts?

@wj25czxj47bu6q wj25czxj47bu6q added the [c] new content Pull requests that add an entirely new article label Oct 22, 2024
@nihil-admirari
Copy link

AMD vs. Intel: https://www.qubes-os.org/doc/system-requirements/

Intel and AMD handle microcode updates differently, which has significant security implications. On Intel platforms, microcode updates can typically be loaded from the operating system. This allows the Qubes security team to respond rapidly to new vulnerabilities by shipping microcode updates alongside other security updates directly to users. By contrast, on AMD client (as opposed to server) platforms, microcode updates are typically shipped only as part of system firmware and generally cannot be loaded from the operating system. This means that AMD users typically must wait for:

  1. AMD to distribute microcode updates to original equipment manufacturers (OEMs), original design manufacturers (ODMs), and motherboard manufacturers (MB); and
    The user’s OEM, ODM, or MB to provide a suitable BIOS or (U)EFI update for the user’s system.
  2. Historically, AMD has often been slow to complete step (1), at least for its client (as opposed to server) platforms. In some cases, AMD has made fixes available for its server platforms very shortly after a security embargo was lifted, but it did not make fixes available for client platforms facing the same vulnerability until weeks or months later. (A “security embargo” is the practice of avoiding public disclosure of a security vulnerability prior to a designated date.) By contrast, Intel has consistently made fixes available for new CPU vulnerabilities across its supported platforms very shortly after security embargoes have been lifted.

Step (2) varies by vendor. Many vendors fail to complete step (2) at all, while some others take a very long time to complete it.

Is it still applicable? Looks like there are no Dell Precision/Latitude laptops with AMD processors, but there are ThinkPad ones.

@wj25czxj47bu6q
Copy link
Member

@nihil-admirari:

AMD vs. Intel: https://www.qubes-os.org/doc/system-requirements/

<snip>

Is it still applicable? Looks like there are no Dell Precision/Latitude laptops with AMD processors, but there are ThinkPad ones.

No, this is not correct today. Both Intel and AMD support microcode updates through the OS, and both also have important firmware components that must be updated by the motherboard vendor.

@wj25czxj47bu6q
Copy link
Member

@duck09:

Have the Microsoft Surface line of laptops been considered? Not the ARM ones (not sure if they they have memory encryption) but the Surface Laptop 6 for example. I'm pretty sure they meet all the requirements and the only downside would be Linux support but this is an article about general Laptop Hardware Security. Thoughts?

We are aware of their existence of course. But the Surface line suffers from a serious lack of technical documentation, and I'm not aware of anyone with access to a modern Surface device who is willing and able to evaluate it against our standards.

Here is some technical documentation from Lenovo for comparison (Dell is also much worse than Lenovo in this regard):

It is possible to get a very detailed idea of Lenovo security features without ever touching a Lenovo laptop (though obviously hands-on time is necessary for a truly complete picture). Dell's business lines are so widely deployed that it is easy to get answers just by searching the internet as a supplement to the official documentation. Neither is true for Surface devices.

@jermanuts
Copy link
Contributor

@wj25czxj47bu6q

No, this is not correct today. Both Intel and AMD support microcode updates through the OS, and both also have important firmware components that must be updated by the motherboard vendor.

https://github.com/QubesOS/qubes-doc/pull/1430/files to address QubesOS/qubes-issues#9485

There is an amd-ucode-firmware package, but it only contains microcode for servers and outdated microcode for Chromebooks. Also, the AMD security website only lists μcode as a mitigation for data center CPUs.

@nihil-admirari
Copy link

nihil-admirari commented Jan 8, 2025

Some news from Dell:

Dell is also killing its Latitude, Inspiron, and Precision branding, it announced today.

Btw, does anybody know anything about the security of HP ProBooks? HP ProBook 450 G10 got HSI 3 (older models are much worse though).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[c] new content Pull requests that add an entirely new article
Development

Successfully merging this pull request may close these issues.

6 participants