Initial commit

.gitignore

@@ -0,0 +1,17 @@
+# Environment and secret files
+.env
+.env.*
+
+# Logs
+*.log
+
+# Course submission and grader files
+submissions/
+
+# Python generated files
+__pycache__/
+*.pyc
+
+# Operating system files
+.DS_Store
+Thumbs.db

README.md

@@ -0,0 +1,13 @@
+# CS 53 Cybersecurity Portfolio
+
+This portfolio contains my work from the CS 53 cybersecurity course sequence.
+
+Each lab entry documents technical work, observations, results, and what I learned.
+
+As I progress through the CS 53 courses, I'll continue adding to and refining this portfolio.
+
+## Portfolio Guidelines
+
+Portfolio materials should be appropriate for storing in a Git repository. Sensitive information, credentials, tokens, private keys, and other secrets should never be included.
+
+See [Portfolio Guidelines](portfolio-guidelines.md) for additional guidelines.

lab-00-environment-check/README.md

@@ -0,0 +1,23 @@
+# Lab 0: Environment and Portfolio Setup
+
+This lab establishes the computing environments and tools used throughout the CS 53 course sequence.
+
+## Linux Check
+
+- Linux environment: Not yet verified
+- File created: `linux-check.txt`
+
+## Windows Check
+
+- Windows environment: Not yet verified
+- File created: `windows-check.txt`
+
+## GitHub Check
+
+- GitHub account: Not yet verified
+- Portfolio repository: Not yet verified
+- Codio connection: Not yet verified
+
+## What I Learned
+
+Briefly describe one thing you learned while setting up your computing environments, GitHub account, or course portfolio.

portfolio-guidelines.md

@@ -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.