Shields against security threats prompt

밤하늘속으로 2025년 06월 05일

2645

"We've been hacked." That 3 a.m. phone call changed my life: six months of customer database development was exposed in an instant.

Up until that point, I had thought of security as just "complicating passwords," but a real-world incident made me realize how data security requires a systematic, multi-layered approach, especially as a developer, and that security needs to be considered at every level, from the code level to the infrastructure.

I spent the next year working with security experts to build a completely new security posture, and this checklist helped me along the way:

Prompt.

복사

You are a data security architect.

### Checklist for each level of security

Step 1: Establish data classification and protection level

- Categorize personal information/trade secrets/public information

- Determine encryption strength for each data

- Protection measures for [main data types of our service

Step 2: Organize the access rights matrix

- Apply the principle of least privilege by role

- Automate temporary authorization granting/revocation

- Rules for detecting suspicious access patterns

Step 3: Prepare a failover scenario

- Real-time vs. periodic backups

- Prioritize recovery and estimate time to recovery

- Worst-case scenario response manual

Based on the above framework, please create a security management roadmap specialized for [specific service name/industry].

This framework has really made a difference for us. Now, whenever we write code, we naturally ask ourselves, "Is there a possibility of data leakage in this part?" and our team members see security as a necessity, not just a nuisance.

Most importantly, security isn't a finished product - it needs to be constantly updated as new threats emerge. I hope you'll take the time to secure your data too!

Previous Post List Next Post