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

Create Security Guideline #73

Closed
lonnieezell opened this issue May 9, 2016 · 10 comments
Closed

Create Security Guideline #73

lonnieezell opened this issue May 9, 2016 · 10 comments
Labels
dev documentation Pull requests for documentation only
Projects
Milestone

Comments

@lonnieezell
Copy link
Member

Should list common security issues, their risks, and how to use the tools within CodeIgniter to prevent or minimize them.

See Rails' Security docs for a great example.

@lonnieezell lonnieezell added the documentation Pull requests for documentation only label May 9, 2016
@lonnieezell lonnieezell added this to the Pre-Alpha 2 milestone May 9, 2016
@Bikerboi
Copy link

Bikerboi commented Dec 8, 2016

I'm Interested to help with this. Although I have just a few questions. what format does the documentation need to be? Would you like any examples that could integrate into the getting started Application that could help show basic examples of the attacks where possible? and how to mitigate them with the supplied tools in CI. Sorry I am new to contributing on GitHub.

@lonnieezell
Copy link
Member Author

@Bikerboi that would be awesome!

We have a first crack at the page but it's missing a lot of the things that I think would be helpful, like realistic examples of how to do this within a CI application, using CI tools. Ideally, I would love to see it fleshed out to something more like Rails' security guide.

The documentation is written in Sphinx's RST format. More info at their docs and in our own guidelines.

Love the fact that you're a first-time contributor! Always exciting to see new people helping out the community. Feel free to ask any questions you have as you move along.

@Bikerboi
Copy link

Bikerboi commented Dec 9, 2016

@lonnieezell That will be no problem.

That is a very good start I like how its heavily aligned to OWASP, I'm an OWASP member.

I will give it a shot to flesh it out quite similar to the Rails guide with realistic examples with CI, that does lead me on to another question,
Does everything work so far in CI4 especially the sample app that's used in the documentation? as I would like to build on from that to help new and experienced devs to implement CIs security features with a little bit of a hands on approach to cement/back up the theory. I will get started this weekend.

I am very excited to help out in this community, I originally came over from hackerone to check out the CI bug bounty program which I am still planning on doing.

@lonnieezell
Copy link
Member Author

That's great to hear that you're an OWASP member! We look forward to any places you find that we're lacking in what we can provide.

The sample app should be working with the current state of CI4, yes. And I think expanding on that is a great idea! Look forward to seeing your work and advice.

@lonnieezell lonnieezell modified the milestones: Alpha, Pre-Alpha 2 Apr 1, 2017
@jim-parry
Copy link
Contributor

@Bikerboi Any update on this? We have an existing guideline (https://bcit-ci.github.io/CodeIgniter4/concepts/security.html), but I had the impression that this issue was intended to expand on that.

@Bikerboi
Copy link

@jim-parry What I have done so far is towards the Owasp top ten 2013 so I am adapting that slowly but surely to the Owasp top ten 2017 list. As it is only in release candidate phase I will have it ready to go when it is actually released which should be this month or next according to Owasp.

@jim-parry
Copy link
Contributor

Looking forward to it!

@jim-parry jim-parry modified the milestones: 4.0.0-alpha, 4.0.0 Sep 27, 2018
@jim-parry jim-parry added the dev label Mar 6, 2019
@jim-parry jim-parry added this to Backlog in Development Mar 6, 2019
@atishhamte
Copy link
Contributor

@jim-parry @lonnieezell any update on this. Is anybody working on the same?

@lonnieezell
Copy link
Member Author

No one is working on this currently.

@lonnieezell
Copy link
Member Author

This won't happen for release. It's a large project to do it well. Closing for now.

Development automation moved this from Backlog to Done Jan 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev documentation Pull requests for documentation only
Projects
Development
  
Done
Development

No branches or pull requests

4 participants