Initial commit
This commit is contained in:
4 files changed
+87
No files matched your search
@@ -0,0 +1,34 @@
|
||||
# CS 53 Portfolio Guidelines
|
||||
|
||||
The CS 53 cybersecurity portfolio is a curated collection of work that demonstrates your technical skills and your ability to explain what you learned.
|
||||
|
||||
Each lab portfolio entry should contain only the materials needed to demonstrate your work, such as:
|
||||
|
||||
- A concise explanation of the activity
|
||||
- Selected commands or code
|
||||
- Sanitized screenshots or diagrams
|
||||
- Results and observations
|
||||
- A short "What I Learned" reflection
|
||||
|
||||
Do not treat your portfolio as a backup of your entire lab environment. Before committing files, review them and remove sensitive, personal, temporary, or unnecessary information.
|
||||
|
||||
Keep your CS 53 portfolio repository private while completing the course. Making portfolio work public should happen only after a deliberate review.
|
||||
|
||||
# CS 53 Portfolio Security Checklist
|
||||
|
||||
Before committing or pushing portfolio material, verify that it does not contain:
|
||||
|
||||
- Passwords
|
||||
- API keys
|
||||
- Access tokens
|
||||
- Session tokens
|
||||
- Authentication cookies
|
||||
- Private keys
|
||||
- Personal information
|
||||
- Unreviewed private IP addresses or network information
|
||||
- Unsanitized security logs
|
||||
- Temporary grader or submission files
|
||||
|
||||
If you are uncertain whether something is safe to include, do not add it to the portfolio.
|
||||
|
||||
Before making any portfolio work public, review it carefully and remove or sanitize anything that should not be shared.
|
||||
Reference in new issue
Block a user