This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Los Angeles

From OWASP

Revision as of 20:58, 8 November 2011 by Richard greenberg (talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Jump to: navigation, search

1 Local News
- 1.1 Sign up for OWASP Los Angeles mailing list, very low volume and spam free.
- 1.2 https://lists.owasp.org/mailman/listinfo/owasp-losangeles
2 Next Chapter Meeting: Wednesday, November 30, 2011 7:00 P.M. - 9:00 P.M. (Note different date)
3 Other Events
4 Archives of Previous Meetings
5 Los Angeles Chapter

Local News

Sign up for OWASP Los Angeles mailing list, very low volume and spam free.

https://lists.owasp.org/mailman/listinfo/owasp-losangeles

<paypal>Los Angeles</paypal>

Next Chapter Meeting: Wednesday, November 30, 2011 7:00 P.M. - 9:00 P.M. (Note different date)

Great talks and free catered dinner for all attendees!

Location:

Symantec
900 Corporate Pointe (just off of Slauson)
Culver City, CA 90230

Please RSVP: http://owasp-november2011.eventbrite.com

Topic: passw3rd

We all know passwords in source code is bad. What many don't know is that passwords in other files are bad too. Moving your passwords to config files, symlinked directories, to even requiring a password to
be typed in upon launch is just silly. Passw3rd is a ruby and java client to create encrypted files which contain your passwords that can be read by source code. Passwords can be checked into SCM and
distributed. The keys are generated per environment and locked down with simple OS RBAC. Included with the project is a POC which uses HSMs to store the passwords, and using passw3rd for the "master"
password for that role.

Some advantages of keeping credentials out of source code are:

Credentials are not passed around when source code is shared.
Unintentional exposure of source code does not reveal credentials.
Read-access to source code can be much more permissive.
Source code can be checked into version control systems without concern for exposure of credentials.
It is easier to change credentials without having to worry about changing all instances.
Leaving credentials in source code leads to poor password management in general. If changing a credential requires you to change code, you
are less likely to want to do it.

https://github.com/oreoshake/passw3rd
http://rubygems.org/gems/passw3rd .

Speaker: Neil Matatall

more details forthcoming.

Topic: Coming Soon

Speaker: Coming Soon

more details forthcoming.

Meeting Sponsor: AlgoSec

Founded in 2003, AlgoSec enables security and operations teams to intelligently manage, analyze and optimize security policies within firewalls, routers and related devices. The software suite increases operational efficiency and improves risk mitigation for organizations worldwide. Today, more than 800 enterprises, MSSPs and auditors in over 40 countries and across all industry verticals use AlgoSec solutions. From mid-sized enterprises and Fortune 500 companies to all Big Four auditing firms, organizations choose AlgoSec for its unique combination of superior technology and commitment to customer satisfaction.

Would you like to speak at an OWASP Los Angeles Meeting?

Call for Papers (CFP) is NOW OPEN. To speak at upcoming OWASP Los Angeles meetings please submit your BIO and talk abstract via email to Tin Zaw. When we accept your talk, it will be required to use the Powerpoint OWASP Template.