Windows Overview #287
Draft
Windows Overview #287
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: oppressor1761 <163018825+oppressor1761@users.noreply.github.com>
Signed-off-by: oppressor1761 <163018825+oppressor1761@users.noreply.github.com>
✅ Deploy Preview for privsec-dev ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
this need to be updated to show 24H2 improvements |
wj25czxj47bu6q
added
[c] new content
This comment was marked as resolved.
This comment was marked as resolved.
wj25czxj47bu6q
requested changes
Oct 28, 2024
There was a problem hiding this comment.
Some of this is good, but some of it is questionable or insufficiently explained.
For example, why should optional diagnostic data be allowed?
Also, we are not going to accept any commands or instructions regarding activation. It is fine to recommend specific editions of Windows, but that's about it.
Signed-off-by: oppressor1761 <163018825+oppressor1761@users.noreply.github.com>
Signed-off-by: oppressor1761 <163018825+oppressor1761@users.noreply.github.com>
Signed-off-by: oppressor1761 <163018825+oppressor1761@users.noreply.github.com>
|
In-depth analysis of Windows architecture and telemetry: https://www.bsi.bund.de/EN/Service-Navi/Publikationen/Studien/SiSyPHuS_Win10/SiSyPHuS_node.html. Some worthy mentions:
They recommend making a hard link for A more hardcore version would be to change Windows Update service to use the hardlink and block all outbound completely, with the exception of Windows Update. |
|
Back in 2012, Windows used non-validating DNSSEC aware local resolver. Have things improved since then? Should I run Unbound locally or in a Linux VM (like with chrony) to do DNSSEC validation? |
|
I think it's better to harden Windows using lgpo, .ppkg and answer files rather than alter group policies one by one manually. It's not easy to remember every custom policies you ever applied without a lgpo. |
|
LGPO text files support comments, e.g.: ; \Control Panel\Personalization
; Prevent enabling lock screen camera
; Enabled
Computer
Software\Policies\Microsoft\Windows\Personalization
NoLockScreenCamera
DWORD:1 |
|
this lgpo can be applied without caution. |
|
This lgpo must be applied with caution |
|
this is the answer file for arm64 devices |
|
this is the provision package |
|
<cpi:offlineImage cpi:source="wim:c:/users/gerbil1183/desktop/install.wim#Windows 11 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
including security and privacy overview.