You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/note-case-study.md
+20-14Lines changed: 20 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,11 +9,11 @@ description: 'How note inc. implements Just-in-Time (JIT) database access contro
9
9
keypage: true
10
10
---
11
11
12
-
> note ([note.com](https://note.com)) is a C2C content platform in Japan that empowers all types of creators and promotes creator economy. note was launched in 2014. note initially implemented an in-house database access system but faced challenges in efficiency and security. By adopting Bytebase, note streamlined access control, enhanced security, and reduced operational costs.
12
+
> note ([note.com](https://note.com)) is a C2C content platform in Japan that empowers creators of all types and promotes the creator economy. Founded in 2014, note initially implemented an in-house database access system but faced challenges with efficiency and security. By adopting Bytebase, note streamlined access control, enhanced security, and reduced operational costs.
13
13
14
14
## Data Access Control Challenges at note
15
15
16
-
Given that note manages data for millions of users, safeguarding user information is paramount. Typically, the internal development team does not have direct access to production databases containing user data. However, accessing these databases is often necessary for troubleshooting production issues. Effectively managing such just-in-time (JIT) access while ensuring compliance is essential for note.
16
+
As note manages data for millions of users, safeguarding user information is paramount. The internal development team does not have direct access to production databases containing user data. However, database access is often necessary for troubleshooting production issues. Effectively managing just-in-time (JIT) access while ensuring compliance is essential for note.
17
17
18
18
## Tackling the Challenge with an In-House Solution
19
19
@@ -28,37 +28,37 @@ To address this challenge, note built a process to manage database access reques
28
28
-**Internal SSH proxy server-based access**
29
29
Developers use the issued credentials to connect through an internal SSH proxy server.
30
30
31
-
However, after running this process for some time, they encountered notable limitations:
31
+
However, after running this process for some time, note encountered several limitations:
32
32
33
-
-**Fragmented process**: Developers had to repeatedly request and configure accounts manually, leading to inefficiencies.
34
-
-**Overly broad permissions**: Developers could access all table columns, including sensitive data that wasn’t necessary for debugging.
35
-
-**High maintenance costs**: Admins had to maintain the in-house tool, SSH proxy server, and troubleshoot workflow issues.
33
+
-**Fragmented process**: Developers had to repeatedly request and configure accounts manually, creating inefficiencies.
34
+
-**Overly broad permissions**: Developers could access all table columns, including sensitive data unnecessary for debugging.
35
+
-**High maintenance costs**: Administrators had to maintain the in-house tool, SSH proxy server, and troubleshoot workflow issues.
36
36
37
37
## Bytebase Provides a One-Stop Database Access Control Solution
38
38
39
-
After extensive research, note’s SRE team selected Bytebase to replace their in-house solution, effectively addressing the challenges of fragmented processes, broad access permissions, and high maintenance costs. Bytebase acts as middleware between humans and databases, ensuring secure, efficient, and compliant just-in-time (JIT) access management.
39
+
After extensive research, note's SRE team selected Bytebase to replace their in-house solution, effectively addressing the challenges of fragmented processes, overly broad access permissions, and high maintenance costs. Bytebase acts as middleware between users and databases, ensuring secure, efficient, and compliant just-in-time (JIT) access management.
Bytebase provides various capabilities to enable more secure and efficient database access, including a unified web-based SQL Editor with fine-grained sensitive data masking and role-based access control.
43
+
Bytebase provides various capabilities that enable more secure and efficient database access, including a unified web-based SQL Editor with fine-grained sensitive data masking and role-based access control.
44
44
45
45

46
46
47
47
### Web-based SQL Editor
48
48
49
-
Bytebase offers a [web-based SQL Editor](https://docs.bytebase.com/sql-editor/overview/) that consolidates all permissions management and data access operations into a single tool. This eliminates the need for the in-house tool, SSH proxy server, and local database clients, allowing developers to submit permission requests and access the database in one place, greatly improving convenience.
49
+
Bytebase offers a [web-based SQL Editor](https://docs.bytebase.com/sql-editor/overview/) that consolidates all permission management and data access operations into a single tool. This eliminates the need for the in-house tool, SSH proxy server, and local database clients, allowing developers to submit permission requests and access databases from one location, significantly improving convenience.
Bytebase offers column-level [dynamic data masking](https://docs.bytebase.com/security/data-masking/overview/) for our Aurora MySQL databases. When granting access permissions to developers for specific tables, sensitive columns can be dynamically masked based on the user's identity during data queries.
55
+
Bytebase offers column-level [dynamic data masking](https://docs.bytebase.com/security/data-masking/overview/) for Aurora MySQL databases. When granting access permissions to developers for specific tables, sensitive columns are dynamically masked based on the user's identity during data queries.
56
56
57
57

58
58
59
59
### Role-Based Data Access Control
60
60
61
-
Bytebase provides role-based database access control, which can implement table-level access control. This permission management is independent of the database account system and is managed by Bytebase. This brings two benefits:
61
+
Bytebase provides role-based database access control that implements table-level access control. This permission management is independent of the database account system and is managed entirely by Bytebase, providing two key benefits:
62
62
63
63
- All permissions and actions can be precisely tracked to individuals.
64
64
- Developers cannot access database credentials.
@@ -86,12 +86,18 @@ Access request notifications will be pushed to Slack.
86
86
87
87
## Next Steps
88
88
89
-
After implementing Bytebase's database access control, the following issues have become apparent. In response, note is considering further leveraging Bytebase's capabilities to address these challenges:
89
+
After implementing Bytebase's database access control, note identified additional opportunities for improvement. In response, note is considering further leveraging Bytebase's capabilities to address these areas:
90
90
91
91
-[CI/CD for DML and DDL changes](https://docs.bytebase.com/change-database/change-workflow/)
92
92
93
-
At present, only read queries are utilized; the aim is to enable modifications for both DML and DDL directly on Bytebase.
93
+
Currently, only read queries are utilized; the goal is to enable both DML and DDL request/review/deploy process directly through Bytebase.
94
94
95
95
-[GitOps workflow with GitHub](https://docs.bytebase.com/gitops/overview/)
96
96
97
-
Given that SQL is currently managed through GitHub Issues in the existing business process, the introduction of GitOps is expected to enhance operational efficiency.
97
+
Since SQL is currently managed through GitHub Issues in the existing business process, introducing GitOps is expected to enhance operational efficiency.
98
+
99
+
---
100
+
101
+
_To learn more, check out our JIT Database Access Whitepaper👇_
0 commit comments