GraphQL security best practices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of query depth limiting in GraphQL?

Query depth limiting restricts how deep a client can nest queries. This helps prevent overly complex queries that can overload the server and cause performance issues.

beginner

Why should you validate incoming GraphQL queries?

Validating queries ensures they follow the schema rules and do not contain malicious or malformed requests. This protects the server from unexpected errors and attacks.

beginner

How does rate limiting improve GraphQL API security?

Rate limiting controls how many requests a client can make in a given time. It prevents abuse like denial-of-service attacks by limiting excessive query traffic.

beginner

What is the role of authentication and authorization in GraphQL?

Authentication verifies who the user is, while authorization controls what data or actions the user can access. Both are essential to protect sensitive data and operations.

intermediate

Why should you avoid exposing internal error details in GraphQL responses?

Exposing detailed errors can reveal sensitive information about the server or database structure. It's safer to return generic error messages to avoid helping attackers.

Which practice helps prevent very complex GraphQL queries that can slow down the server?

A Schema stitching

B Using fragments

C Query depth limiting

D Batching queries

Query depth limiting restricts how deeply queries can nest, preventing overly complex requests.

What does rate limiting protect a GraphQL API from?

A Unauthorized data access

B Excessive request flooding

C Schema validation errors

D Slow network connections

Rate limiting controls the number of requests to prevent flooding and denial-of-service attacks.

Why is it important to validate GraphQL queries before execution?

A To encrypt data in transit

B To improve client UI performance

C To cache query results

D To ensure queries match the schema and avoid malicious requests

Validation ensures queries are safe and conform to the schema, protecting the server.

What is the difference between authentication and authorization in GraphQL security?

A Authentication checks user identity; authorization controls access rights

B Authentication encrypts data; authorization decrypts data

C Authentication limits query depth; authorization limits query complexity

D Authentication caches queries; authorization logs queries

Authentication verifies who the user is; authorization decides what they can do.

What should you avoid including in GraphQL error responses to improve security?

A Detailed internal server information

B User-friendly messages

C Error codes

D Generic error messages

Detailed internal errors can reveal sensitive info to attackers, so avoid exposing them.

Explain key security best practices to protect a GraphQL API from abuse and attacks.

Think about how to control query complexity, user access, and server responses.

Describe how authentication and authorization work together to secure GraphQL data.

Consider who the user is and what they are allowed to do.

Practice

1. What is the main purpose of authentication in GraphQL security?

easy

A. To encrypt the data sent between client and server

B. To limit the number of queries a user can make

C. To verify the identity of the user making the request

D. To format the GraphQL schema correctly

Solution

1. Step 1: Understand authentication role

   Authentication checks who the user is before allowing access.

2. Step 2: Differentiate from other security measures

   Limiting queries and encryption are different security aspects, not authentication.

3. Final Answer:

   To verify the identity of the user making the request -> Option C

4. Quick Check:

   Authentication = Verify user identity [OK]

Hint: Authentication means checking who you are [OK]

Common Mistakes:

• Confusing authentication with authorization
• Thinking authentication limits query size
• Mixing authentication with encryption

2. Which of the following is the correct way to limit query complexity in a GraphQL server?

easy

A. Allow unlimited queries and rely on client honesty

B. Use SQL injection to filter queries

C. Disable authentication to speed up queries

D. Use a middleware that calculates query depth and rejects too deep queries

Solution

1. Step 1: Identify query complexity control

   Middleware can analyze query depth and reject overly complex queries to protect the server.

2. Step 2: Eliminate incorrect options

   Allowing unlimited queries or disabling authentication weakens security; SQL injection is an attack, not a defense.

3. Final Answer:

   Use a middleware that calculates query depth and rejects too deep queries -> Option D

4. Quick Check:

   Limit query complexity = Middleware checks depth [OK]

Hint: Middleware can block too complex queries [OK]

Common Mistakes:

• Ignoring query complexity limits
• Confusing SQL injection with security measure
• Disabling authentication to improve speed

3. Given this GraphQL resolver snippet, what will happen if a user without proper role tries to access the data?

const resolver = (parent, args, context) => {
  if (!context.user.roles.includes('admin')) {
    throw new Error('Access denied');
  }
  return getData();
};

medium

A. An error 'Access denied' will be thrown for non-admin users

B. The data will be returned regardless of user role

C. The server will crash due to missing roles

D. The resolver will ignore the role check and return null

Solution

1. Step 1: Analyze role check in resolver

   The code checks if the user roles include 'admin'. If not, it throws an error.

2. Step 2: Understand error handling

   Throwing an error stops execution and returns 'Access denied' to the client.

3. Final Answer:

   An error 'Access denied' will be thrown for non-admin users -> Option A

4. Quick Check:

   Role check fails = Error thrown [OK]

Hint: Throw error if user lacks role [OK]

Common Mistakes:

• Assuming data returns without role check
• Thinking server crashes on missing role
• Believing null is returned instead of error

4. Identify the security issue in this GraphQL server setup:

const server = new ApolloServer({
  typeDefs,
  resolvers,
  context: ({ req }) => ({ user: req.user })
});

// No rate limiting or query complexity checks applied

medium

A. Missing authentication in context setup

B. No rate limiting or query complexity protection

C. Resolvers are not defined

D. Using ApolloServer is insecure

Solution

1. Step 1: Review context and security features

   Context passes user info, so authentication may exist, but no rate limiting or complexity checks are shown.

2. Step 2: Identify missing protections

   Without rate limiting and query complexity checks, server is vulnerable to overload and abuse.

3. Final Answer:

   No rate limiting or query complexity protection -> Option B

4. Quick Check:

   Missing limits = Vulnerable server [OK]

Hint: Always add rate limits and complexity checks [OK]

Common Mistakes:

• Assuming ApolloServer is insecure by default
• Confusing missing resolvers with security issue
• Ignoring rate limiting importance

5. You want to protect your GraphQL API from abuse by limiting both query complexity and request rate. Which combination of methods is best practice?

hard

A. Implement query depth analysis middleware and use a rate limiter like Redis to track requests

B. Only use authentication tokens without any query or rate limits

C. Disable introspection to prevent all queries

D. Allow unlimited queries but log all requests for later review

Solution

1. Step 1: Understand query complexity protection

   Middleware that analyzes query depth helps prevent expensive queries that overload the server.

2. Step 2: Understand rate limiting

   Using a rate limiter like Redis tracks and limits how many requests a user can make in a time window.

3. Step 3: Evaluate other options

   Authentication alone doesn't limit abuse; disabling introspection breaks development; logging alone doesn't prevent abuse.

4. Final Answer:

   Implement query depth analysis middleware and use a rate limiter like Redis to track requests -> Option A

5. Quick Check:

   Combine depth check + rate limiter = Best protection [OK]

Hint: Use middleware plus rate limiter for best security [OK]

Common Mistakes:

• Relying only on authentication
• Disabling introspection breaks tools
• Logging without limiting requests