Skip to content

Commit 8475abb

Browse files
committed
blog: improve note case study
1 parent 8dc98fb commit 8475abb

File tree

6 files changed

+21
-15
lines changed

6 files changed

+21
-15
lines changed

content/blog/note-case-study.md

Lines changed: 20 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,11 @@ description: 'How note inc. implements Just-in-Time (JIT) database access contro
99
keypage: true
1010
---
1111

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.
1313
1414
## Data Access Control Challenges at note
1515

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

1818
## Tackling the Challenge with an In-House Solution
1919

@@ -28,37 +28,37 @@ To address this challenge, note built a process to manage database access reques
2828
- **Internal SSH proxy server-based access**
2929
Developers use the issued credentials to connect through an internal SSH proxy server.
3030

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:
3232

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

3737
## Bytebase Provides a One-Stop Database Access Control Solution
3838

39-
After extensive research, notes 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.
4040

4141
![sso-bb](/content/blog/note-case-study/sso-bb.webp)
4242

43-
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.
4444

4545
![jit](/content/blog/note-case-study/jit.webp)
4646

4747
### Web-based SQL Editor
4848

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

5151
![sql-editor](/content/blog/note-case-study/sql-editor.webp)
5252

5353
### Dynamic Data Masking
5454

55-
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.
5656

5757
![ddm](/content/blog/note-case-study/ddm.webp)
5858

5959
### Role-Based Data Access Control
6060

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:
6262

6363
- All permissions and actions can be precisely tracked to individuals.
6464
- Developers cannot access database credentials.
@@ -86,12 +86,18 @@ Access request notifications will be pushed to Slack.
8686

8787
## Next Steps
8888

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:
9090

9191
- [CI/CD for DML and DDL changes](https://docs.bytebase.com/change-database/change-workflow/)
9292

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

9595
- [GitOps workflow with GitHub](https://docs.bytebase.com/gitops/overview/)
9696

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👇_
102+
103+
[![jit-whitepaper-cover](/content/whitepaper/just-in-time-database-access/cover-horizontal.webp)](/content/whitepaper/just-in-time-database-access/bytebase-whitepaper-just-in-time-database-access-best-practices.pdf)
-12.3 KB
Loading
30.2 KB
Loading
13.7 KB
Loading
-14.3 KB
Binary file not shown.

src/app/[locale]/whitepaper/just-in-time-database-access/page.tsx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ export default function Page() {
1515
<div className="col-span-5 lg:col-span-8 sm:col-span-full">
1616
<div className="relative w-full" style={{ paddingBottom: 'calc(22/17 * 100%)' }}>
1717
<Image
18-
src="/content/whitepaper/just-in-time-database-access/cover.webp"
18+
src="/content/whitepaper/just-in-time-database-access/cover-vertical.webp"
1919
alt="Just-in-time Database Access Whitepaper Cover"
2020
width={612}
2121
height={792}

0 commit comments

Comments
 (0)