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

Tools to detect security vulnerabilities #1927

Closed
Tracked by #1676 ...
jonathanbossenger opened this issue Oct 9, 2023 · 10 comments
Closed
Tracked by #1676 ...

Tools to detect security vulnerabilities #1927

jonathanbossenger opened this issue Oct 9, 2023 · 10 comments
Assignees
Labels
[Content] Published Marks closed issues as content that was actually published.

Comments

@jonathanbossenger
Copy link
Collaborator

jonathanbossenger commented Oct 9, 2023

Details

  • Content type (Online Workshop, Lesson, Course, Tutorial, or Lesson Plan): Lesson
  • Content title: Tools to detect security vulnerabilities
  • Topic description: Discuss tools and resources to help detect and prevent security vulnerabilities
  • Audience (User, Developer, Designer, Contributor, etc.): Developer
  • Experience Level (Beginner, Intermediate, Advanced, Any): Beginner

Learning Objectives

  • Identify plugin solutions that can test plugins or themes for vulnerabilities
  • Install a command line tool that can scan for vulnerabilities
  • Define tools that can be installed in code editors to check for vulnerabilities
  • Identify online resources to keep up to date with changing web security

Related Resources and Other Notes

Automation Code

@smileBeda
Copy link

smileBeda commented Oct 13, 2023

I am adding this here as it seems most appropriate:

A potential instruction as of how to incorporate wpcs into development workflow would possibly deserve a place here.
The plugin review plugin is surely good but imo it’s better to just develop safely from the start, in the IDE, not go forth and back with scanners post-development.
Also another tool that has saved my belated posterior a several times already is sonar cloud scanner. It’s free and has a few good things wpcs doesn’t look directly for.

@jonathanbossenger
Copy link
Collaborator Author

Thanks @smileBeda this is the perfect spot to add it.

I was thinking that renaming this lesson from just being focused on the plugin security checker, and rather "Useful tools to detect security vulnerabilities" would be a good switch, and then we can include these tools.

Concerning the Sonar Cloud Scanner, I will need to check with the training team. We do have specific guidelines about suggesting paid services (I know there's a free trial, but ultimately it's a paid product, and I have to follow those guidelines.

@smileBeda
Copy link

smileBeda commented Oct 13, 2023

Sonar Cloud is 100% free, forever (And easily integrated to VS Code, etc, for free too).
It is only paid (10 USD per month) if you require scans on private repositories.

However, it is not a necessity to mention that service... if we can even just bring WPCS more to the dev attention it is already a huge gain.

@jonathanbossenger
Copy link
Collaborator Author

jonathanbossenger commented Oct 13, 2023

Sonar Cloud is 100% free, forever

Thanks, can you point me to a link that shows that, I can't find that anywhere on the website.

Edit: Oh, wait, found it https://www.sonarsource.com/open-source-editions/.

@github-project-automation github-project-automation bot moved this from 🚧 Drafts in Progress to 📜 Published or Closed in LearnWP Content - Development Jan 22, 2024
@github-project-automation github-project-automation bot moved this from 📜 Published or Closed to 🚧 Drafts in Progress in LearnWP Content - Development Jan 27, 2024
@jonathanbossenger jonathanbossenger changed the title Using the WordPress plugin checker Using the WordPress plugin and theme checkers Feb 29, 2024
@jonathanbossenger jonathanbossenger changed the title Using the WordPress plugin and theme checkers Tools to detect security vulnerabilities Feb 29, 2024
@jonathanbossenger
Copy link
Collaborator Author

03.Tools.to.detect.security.vulnerabilities.mp4

Video ready for review

Please follow the Guidelines for reviewing content to review this lesson.

@jonathanbossenger jonathanbossenger moved this from 🚧 Drafts in Progress to 🔎 Ready for Review in LearnWP Content - Development Mar 28, 2024
@ironnysh
Copy link

Tutorial/Lessons Review Checklist

  • Learning outcomes/objectives are clear.
  • Technical concepts introduced in the content are accurate.
  • The speed of demonstrations are easy to follow.
  • The narration audio matches what is shown visually.
  • Spelling and grammar are correct.
  • Sound quality is consistent throughout the video.
  • Brand Usage Guidelines and Promotional Guidelines are being followed.
  • Media assets are all in the public domain (CC0).

Great tutorial, @jonathan! Provides a solid closure to this miniseries.

@jonathanbossenger
Copy link
Collaborator Author

https://wordpress.tv/2024/05/11/tools-to-detect-security-vulnerabilities/

@pricelessopoku
Copy link

pricelessopoku commented May 11, 2024

Please tick all items you've confirmed:

  • Learning outcomes/objectives are clear.
  • Technical concepts introduced in the content are accurate.
  • The speed of demonstrations are easy to follow.
  • The narration audio matches what is shown visually.
  • Spelling and grammar are correct.
  • Sound quality is consistent throughout the video.
  • Brand Usage Guidelines and Promotional Guidelines are being followed.
  • Media assets are all in the public domain (CC0).

Great video @jonathanbossenger, Clear, concise, and easy to follow.

@jonathanbossenger
Copy link
Collaborator Author

@jonathanbossenger
Copy link
Collaborator Author

//publish

@github-actions github-actions bot added the [Content] Published Marks closed issues as content that was actually published. label May 11, 2024
@github-project-automation github-project-automation bot moved this from 🔎 Ready for Review to 📜 Published or Closed in LearnWP Content - Development May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Content] Published Marks closed issues as content that was actually published.
Projects
Status: 📜 Published or Closed
Development

No branches or pull requests

5 participants