About Me

My name is Cameron. I am a Full-Stack Developer based in Nashville.

I'm a Full-Stack Developer who's familiar with all concepts and layers in computer software building from the front-end to the back-end and all of the OS's in between. Layers of the Full Stack are server, network, hosting environment, data modeling, business logic, API layer / Action layer / MVC, User interface, User experience, and understanding what the customer and the business need. I'm not concerned with what a program does, but how well the program does it. I'm subscribed to GitHub Pro and use a Git branching model for the software development process. Private repositories are only accessible to me, people I explicitly share access with, and, for organization repositories, certain organization members. I have mastered the core aspects of computer programming that are valid across programming languages which covers the following topics: Algorithms, Complex Data Types, Data Access, Productivity and Quality, Program Flow, Program Structure, Programming Paradigms, User Interface, Variables, Data Types, Output and Print, Arrays, Conditional Statements, Loops, and Operators.

Security

What are the top security risks that I look for?

My mission is to make software security visible, so that individuals and organizations are able to make informed decisions. Consider the business value of the affected data and the platform running the interpreter. All data could be stolen, modified, or deleted. Could your reputation be harmed? Also, consider the business impact of public exposure of the vulnerability. The system could be completely compromised without you knowing it. All your data could be stolen or modified slowly over time. Recovery costs could be expensive. To safeguard your business, it is essential to implement various protective measures.

• SQL Injection
• Broken Authentication and Session Management
• Cross-Site Scripting
• Broken Access Control
• Security Misconfiguration
• Sensitive Data Exposure
• Insufficient Attack Protection
• Cross-Site Request Forgery (CSRF)
• Using Components with Known Vulnerabilities
• Underprotected APIs
• Security Logging and Monitoring Failures
• Server-Side Request Forgery
• Cryptographic Failures
• Botnet Attacks
• Distributed Denial-of-Service (DDoS) Attack
• Blacklisted IPs
• Backdoor Access
• Access to Restricted Folder
• Insecure Deserialization
• XML External Entities (XXE)
• HTTP Verb Tampering
• File Inclusion
• Command Injection
• Firewall Bypass
• Card Testing Fraud Attacks
• Clickjacking Attacks
• Anonymous Proxies
• Improper User Agents
• SSL Stripping