Skip to content

Update InformationSecurity with USB & secure wipe policy#342

Open
siddharth-krishna wants to merge 2 commits intomainfrom
sid/update-infosec
Open

Update InformationSecurity with USB & secure wipe policy#342
siddharth-krishna wants to merge 2 commits intomainfrom
sid/update-infosec

Conversation

@siddharth-krishna
Copy link
Copy Markdown
Member

Updates InformationSecurity with USB & secure wipe policy

Checklist

  • I have checked the Deploy Preview link in the netlify bot's comment, and my changes look good
  • I tested my contribution locally, and it seems to work fine.
  • Code and workflow changes are sufficiently documented.
  • If new pages are added, maintainers are assigned for that document.
  • If the document falls under a controlled category, a controlled document banner is present.

@netlify
Copy link
Copy Markdown

netlify bot commented Apr 6, 2026

Deploy Preview for wonderful-mousse-057100 ready!

Name Link
🔨 Latest commit b644d7a
🔍 Latest deploy log https://app.netlify.com/projects/wonderful-mousse-057100/deploys/69dd0b7f1e72b70008ebb08f
😎 Deploy Preview https://deploy-preview-342--wonderful-mousse-057100.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 project configuration.

1. Preparation: The employee creates a ShredOS bootable USB.
1. The Witness Call: The employee starts a video call with the Head of People or Information Security Manager from their phone.
1. The Identification:
- The employee points the phone camera at the laptop screen showing the Serial Number (using the dmidecode command we discussed earlier or the BIOS screen).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

dmidecode command we discussed earlier

I think this part is missing

1. Preparation: The employee creates a ShredOS bootable USB.
1. The Witness Call: The employee starts a video call with the Head of People or Information Security Manager from their phone.
1. The Identification:
- The employee points the phone camera at the laptop screen showing the Serial Number (using the dmidecode command we discussed earlier or the BIOS screen).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'm not sure if the dmidecode command will work on Windows as well. (since we also have Windows OET devices)

1. The Identification:
- The employee points the phone camera at the laptop screen showing the Serial Number (using the dmidecode command we discussed earlier or the BIOS screen).
- The employee shows the physical Asset Tag or serial number sticker on the bottom of the device.
1. The Initiation: The employee boots into ShredOS, selects the drive, and chooses the PRNG Stream or Zero Fill (1 pass is sufficient for modern SSDs).
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Reading through the readme of ShredOS, I think we might need to distinguish between HDD, SSD and NVMe. It looks like for SSD we would need the hdparm command and for NVMe nvme.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

@naumek could you please suggest an edit for this line accordingly?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Maybe something like this?

1. Identification: Film the Serial Number via BIOS/CLI (dmidecode) and the physical Asset Tag sticker (if present).
2. Initiation: Boot ShredOS; use nwipe for HDDs, hdparm for SATA SSDs, or nvme-cli for NVMe drives.

@siddharth-krishna
Copy link
Copy Markdown
Member Author

@stefan-oet thank you. Could you please add the necessary changes to the PR and merge it in?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants