Implementing W3OSC's account configuration guides into Frameworks #305
Conversation
… the configuration
…ices, incident response, individual security, multi-signature setups, and various account configurations across platforms.
|
@DicksonWu654 is attempting to deploy a commit to the Security Alliance Team on Vercel. A member of the Team first needs to authorize it. |
…in URLs and enhance clarity. Add new contributor entry for Auditware in contributors.json and expand fetched tags for improved categorization.
|
@mattaereal & @joevanloon. Here's the integration of W3OSC's specific guides into frameworks. Matta would it be possible for you to review all the controls to make sure we're okay putting them into frameworks. Joe lmk if I missed anything! |
…standards URL across multiple platforms, ensuring consistency in the adaptation source for configuration checklists.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
There's a clear overlap with the Community Management section content and this. Additionally, this should not be at a domain-level framework. We need to discuss this further |
- Added a new contributor, Auditware, to the contributors list. - Introduced a summary section highlighting key security takeaways for Discord server management. - Reorganized and expanded security measures, including checklists for individual accounts, team members, and admins. - Streamlined guidelines for server settings, roles, permissions, and moderation practices to improve clarity and usability. - Updated various sections to ensure comprehensive coverage of security best practices and community management strategies.
…ganizations. This includes the deletion of configuration guides and checklists that are no longer relevant, streamlining the account security resources.
NFTDreww
left a comment
NFTDreww
left a comment
There was a problem hiding this comment.
Reviewed and Approved. Going to go over after commit to add additional content.
- Added a new contributor, Auditware, to the contributors list. - Introduced a summary section with key takeaways for improving Google account security. - Expanded the security measures section with detailed checklists for individuals, team members, and admins. - Reorganized content for clarity, including guidelines on account settings, 2FA, and third-party app access. - Updated various sections to ensure comprehensive coverage of best practices for account security.
… and organizations. This includes the deletion of configuration guides and checklists that are no longer relevant, streamlining the account security resources.
…rganizations. This includes the deletion of configuration guides and checklists that are no longer relevant, streamlining the account security resources.
…organizations. This includes the deletion of configuration guides and checklists that are no longer relevant, streamlining the account security resources.
There was a problem hiding this comment.
Seems like there is an error at line 455 in the vocs.config.ts ↓
✘ [ERROR] Expected "]" but found ":"
vocs.config.ts:455:14:
455 │ text: 'Treasury Operations',
│ ^
╵ ]
the Treasury Operations fw is not in {} brackets
Also, copy/pasting the file in my editor, i noted other errors for brackets misplacing/missing.
Let me know when you update so i can approve the deployment
- Introduced comprehensive security guides for Telegram and Twitter/X, detailing best practices for account protection, including two-factor authentication, privacy settings, and device security. - Updated the main overview to include links to the new guides, enhancing navigation for users seeking security information for these platforms. - Added relevant contributor information to the new guides for proper attribution. Co-authored-by: mattaereal
- Introduced a new section for Treasury Operations in the configuration file, enhancing the documentation structure. - Marked the section as development-related to indicate its current status. - Improved organization of the configuration for better user navigation and access to relevant information.
- Removed outdated account security guides for individuals and organizations, streamlining the documentation structure. - Introduced new security guides for GitHub, GoDaddy, Linear, Mercury, Notion, Render, Sentry, Signal, Slack, Trello, and Vercel, enhancing coverage of best practices for securing accounts across various platforms. - Updated the main guides overview to include links to the new security guides, improving navigation for users seeking security information. - Enhanced the vocs.config.ts file to reflect the updated structure and include new items for the added security guides. Co-authored-by: auditware
Fixed! Sorry aobut that! |
|
@NFTDreww @mattaereal ready for review now! |
|
Until we wait for Drew, how do we all think about sub-categorizing the guides? There could be guides for almost everything; the list could get very long very quickly, and it's not as easy to understand from their names as in other categories. In this specific PR, these are more about configuring platforms to be more secure, not a guide on how to implement an IR template or how to go through your machine to look for malware. Order, and categorizing is imminent!~ |
- Restructured the account management section in vocs.config.ts to include a new "Account Management" category, consolidating security guides for various platforms. - Added detailed security guides for Discord, GitHub, GoDaddy, Linear, Mercury, Notion, Render, Sentry, Signal, Slack, Trello, and Vercel, enhancing user access to best practices for securing accounts. - Updated links in existing documentation to reflect the new guide paths, improving navigation and accessibility for users seeking security information. - Removed outdated links and streamlined content for clarity and organization. Co-authored-by: auditware
…larity - Changed the "Account Management" section in vocs.config.ts to be collapsed by default, enhancing user experience. - Updated the index.mdx file to clarify that it is auto-generated and provided a note for users to navigate via the sidebar. - Revised the overview.mdx file to include contributor information for better attribution. - Renamed the account management index.mdx file to reflect its title accurately and expanded the list of security guides available under this section, improving accessibility to essential resources. Co-authored-by: dickson, nftdreww
4 participants
Frameworks PR Checklist
Thank you for contributing to the Security Frameworks! Before you open a PR, make sure to read information for contributors and take a look at the following checklist:
Implementing W3OSC's account configuration guides into Frameworks
vocs.config.tsadding thedev: trueparameter