3 ms·
> Could end my career. Very unlikely. Stick to good practices. If you are asked to do something that's bad for security, raise your objections in written form
by perlgeek 5y ago
> Could end my career.
Very unlikely.
Stick to good practices. If you are asked to do something that's bad for security, raise your objections in written form (email/tickets).
Security isn't only your responsibility; it's also the product manager's and the security team's responsibility.
All together this means that it's very hard for a company to convincingly blame a single developer for an incident. Maybe they fire you as a scapegoat, but that isn't very likely, and it should be far from career ending.
- spacemanmatt 5y ago> Security isn't only your responsibility This. As a developer, your security-aligned goals should include code review, readable/auditable code, configuration options that support testing/QA, features that operate on a principle of least surprise to the user, and other things like these. Security is ultimately a blended practice.