
The most efficient way to secure your WordPress site without a plugin is by configuring custom user permissions based on roles, with a reverse proxy. This way, you can easily set and configure the correct permissions based on user roles (RBAC) for your WordPress files and folders.

## What are WordPress file permissions?

WordPress file permissions are the rules that allow users control over a file or folder or directory based on the defined role based access control (RBAC). With the correct WordPress file permissions set, users won’t access any unauthorized folders and they will easily know what are the “do’s” and “don’ts”. For example, any user at a junior level in an organization will not be able to access the files and folders which are authorized only for employees at a senior level. This is possible through role based access control configured for the WordPress file permissions.

### What is role based access control ( RBAC ) ? {#rbac}

Role based access control (RBAC) means allowing access to users to a directory based on the set user roles and permissions. With a defined role based access control (or RBAC) users access levels throughout the organization and protect their data at the same time.

### Top 3 reasons why you need to set WordPress file permissions. {#three-reason}

**1. Role based access control (RBAC):** Control which user can access which folder and data items.

**2. Monitor user actions:** It helps in monitoring and analyzing every single access request sent from a user for potential threats.

**3. Update user roles and permissions**: You can easily make changes to a user’s role and access levels by making the changes in the server itself.


### How to secure your WordPress site files and folders? {#secure-folder}

WordPress files can be secured with the help of a reverse proxy server. At the time of login, based on the user roles and permission attributes defined in the IDP (or user pool). This way, user roles will be mapped along with access based WordPress file permissions. Hence, no unauthorized user will be able to access the WordPress files and folders of an organization and data breaches will be prevented.

### 6 Advantages of securing WordPress file permissions with reverse proxy. {#six-advantages}

**1. Set user permissions:** It correctly maps all the user roles defined at the time of SSO Login based WordPress file permissions.

**2. Set IP restriction:** We can set IP restriction to prevent access from devices not on the organization’s network. You can also add or block an entire range of IP addresses.

**3. Set Device Restriction:** We can set device restriction where the admin can set WordPress file permissions to block devices trying to access WordPress files and folders based on the authorized MAC address of the user device.

**4. Set Location restriction:** With Location restriction, you can block access to your WordPress files and folders based on geographical locations to prevent any unauthorized access attempts.

**5. Monitor Traffic:** The admin can monitor traffic coming towards their WordPress site. This way the admin can check who and when an unauthorized user tried to access the WordPress files and folders.

**6. Set Rate Limiting:** With rate limiting, the admin can set the amount of traffic reaching the WordPress site to prevent an increase in the number of access attempts of WordPress files and folders.

### How does access control secure WordPress websites based on user role? {#access-control-wordpress}

Suppose we have 2 users, Joe and Eddie. We have 2 separate sites on WordPress (Website#1 and Website#2) that we are redirected to from the origin website. The access to those sites will be granted based on the user roles and permissions defined.

In our use case, Joe has access to Website#1 and Eddie has access to Website#2. Now say Joe and Eddie both, try to access  Website#1. The users will send an OAuth request to the website via the reverse proxy. On the role based access control specified (or RBAC) for each user and credentials entered, the site will send an OAuth response back.  If the user role to access the site is valid, the request will be authenticated or else it will be declined. Hence in our use case, Joe will be granted access to Website #1 and Eddie’s request will be denied by the reverse proxy itself.

The main requirement for us here is WordPress role based access control (or RBAC), and because of that requests sent to sites by any user will be monitored and proper authentication will run. This way any user from a different role will not be able to access the WordPress website resources.

**If the user role is valid to access the website.**

Suppose a client wants to access a site, first an OAuth request will be sent to the website’s IDP via the miniOrange Reverse Proxy server. The site will send an OAuth response back to the reverse proxy server and if the OAuth response message is valid, the user will be granted access to the WordPress site data.

![bot traffic for without reverse proxy](/blog/assets/2023/user-role-access-subsites-granted.webp)

**If the user role is invalid to access the website.**

Suppose a client wants to access a site, first an OAuth request will be sent from to the website IDP, via the miniOrange Reverse Proxy server. The site will send an OAuth response back to the reverse proxy server and if the OAuth response message is not valid, the user will be denied access then and there by the miniOrange Reverse Proxy.

![bot traffic for with reverse proxy](/blog/assets/2023/user-role-access-subsites-denied.webp)

### Other features of miniOrange reverse proxy {#features}

**1.** User access control setup and management.

**2.** Bot traffic mitigation.

**3.** Load balancing.

**4.** IP restriction.

**5.** Content caching.

**6.** Traffic monitoring and analysis.

### In Summary {#conclusion}

WordPress file permissions can be configured to secure and prevent unauthorized access by setting role based access control (RBAC) for each user with the help of a reverse proxy server. Based on the roles users’ play in an organization, exclusive access to data and information is granted and secured by properly monitoring the requests sent.

So what are you waiting for? Drop us a query at [info@xecurify.com](mailto:info@xecurify.com) and we will get right back to you to address all your needs.

### Reference links  {#reference-links}

1. [1. Gmail Group Based Access Control With Google Workspace CASB.](https://www.miniorange.in/blog/gmail-group-based-access-control-with-google-workspace-casb/)
2. [2. MS-365 CASB for Microsoft Teams Security.](https://www.miniorange.in/blog/ms-365-casb-for-microsoft-teams-security/)





WordPress site file permissions basically define which users can perform what actions on them. Securing WordPress files and folders provide better protection against vulnerabilities in your site code, security against unstable plugins, and any threats against your WordPress site.

How to set up WordPress role based access control to secure site folders?


**What is API Rate Limiting and How Does It Work?**

An API rate limit is a restriction that some APIs impose on the number of requests that can be made within a certain time period. It is put in place to prevent excessive usage of the API and to ensure that it is used fairly by all users.

The rate limit specifies the maximum number of requests that can be made per unit of time, such as per second, minute, or hour. If a user exceeds the rate limit, the API may stop responding to their requests or may return an error code.

Rate limiting is an important mechanism to prevent abuse of APIs, to manage server resources, and to ensure that all users have a fair and equal opportunity to use the API. It is common for APIs to provide information on the rate limits in their documentation to help developers understand how to use the API responsibly.

### What is the purpose of rate limiting? {#purpose-of-rate-limiting}

The purpose of rate limiting is to restrict the amount of traffic that is allowed to pass through a system, service, or API within a certain period of time. Rate limiting is a common technique used in computer networking, web applications, and other online services to prevent abuse, reduce the risk of system overload, and improve overall performance and security.

Rate limiting can help to prevent denial-of-service (DoS) attacks, brute-force attacks, and other types of abuse that can overwhelm a system or service by generating an excessive number of requests. By limiting the number of requests that can be processed within a given time period, rate limiting can help to protect against these types of attacks.

Rate limiting can also be used to optimize system performance by preventing unnecessary or redundant requests from being processed. This can help to reduce the load on servers, improve response times, and ensure that the system remains responsive even under heavy load.

Overall, rate limiting is an important tool for maintaining the reliability, availability, and security of online systems and services.

### Some common attacks prevented by Rate Limiting {#attacks-prevented-by-rate-limiting}

- DDoS : A DDoS (Distributed Denial of Service) attack is a type of cyber attack where a large number of devices or computers are used to flood a server, network, or API with a huge amount of traffic, making it unavailable to legitimat users. In the context of APIs, a DDoS attack can be launched against an API to overwhelm its servers with requests, which can result in the API becoming unavailable, unresponsive, or unusable. This can be a serious problem, especially for businesses and organizations that rely on their APIs to provide critical services to their customers.
DDoS attacks can take various forms, including UDP floods, SYN floods, HTTP floods, and more. These attacks are often carried out using botnets, which are networks of compromised devices that can be controlled by a single attacker to launch an attack on a target.
To mitigate the risk of DDoS attacks, API providers can implement various security measures, including rate limiting, traffic filtering, and using a content delivery network (CDN) to distribute traffic across multiple servers. Additionally, it’s important to stay up-to-date on the latest security threats and vulnerabilities, and to have a plan in place to respond to an attack if one occurs.
- Brute force Attack: A brute force attack is a type of cyber attack in which an attacker uses automated software to guess a username and password or other authentication credentials in order to gain access to an API.
In the context of APIs, a brute force attack can be launched by an attacker who wants to gain unauthorized access to an API’s endpoints or data. The attacker typically uses a list of possible usernames and passwords and systematically tries each one until the correct credentials are found, or until the attacker gives up.
APIs are particularly vulnerable to brute force attacks because they often provide access to sensitive data or critical functions, such as financial transactions, without requiring additional layers of authentication. If an attacker successfully guesses a set of credentials, they could potentially access or modify sensitive data, or even take control of the API.
To mitigate the risk of brute force attacks, API providers can implement various security measures, including rate limiting, using strong authentication protocols (such as two-factor authentication), and monitoring access logs for suspicious activity. It’s also important to encourage API users to choose strong, unique passwords and to regularly change their credentials to reduce the likelihood of a successful brute force attack.
- Web scraping: Web scraping can potentially be used as an attack against API services. Here are a few ways web scraping can be used as an attack against an API service:
- Rate Limit Bypass : Many APIs have rate limits in place to prevent excessive usage and to protect the API from overloading. Web scrapers can be used to bypass these rate limits by mimicking the behavior of a legitimate user, making it harder for the API to detect and block abusive usage.
- Data Scraping : Web scrapers can be used to scrape data from an API, allowing an attacker to collect sensitive information or gain insights into the workings of the API that could be used to exploit weaknesses.
- Denial of Service : Web scrapers can be used to launch a distributed denial-of-service (DDoS) attack against an API service by overwhelming it with requests.
- Credential Stuffing : Web scrapers can be used to harvest usernames and passwords from a website or service, and then use those credentials to access APIs. To prevent web scraping attacks against API services, API providers can implement measures such as rate limiting, CAPTCHAs, and other anti-bot protections. They can also use API management tools to monitor and analyze API traffic for signs of abuse or suspicious activity. Additionally, API providers can require authentication and authorization for API access, and use techniques such as encryption and tokenization to protect sensitive data transmitted through the API.

**How will Rate Limiting be enabled in miniOrange API Gateway ?**

Enabling rate limiting in an miniOrange API Gateway involves several steps. Here’s a general overview of the process:

- Create a Policy : First, you’ll need to create a Policy in the API Gateway dashboard. This can be done through the miniOrange Console.
- Set up a quota : A quota is a limit on the number of requests that can be made to an API over a specified time period. You’ll need to set up a quota for your API. This can be done through the miniOrange API Gateway dashboard.
- Set up a rate limit : A rate limit is a limit on the number of requests that can be made to an API within a specified time period. You’ll need to set up a rate limit for your API.
Save the policy to the API dashboard: Once you’ve submitted your policy , you’ll need to attach it to the API stage that you want to rate limit. This can be done through the miniOrange dashboard Console.
- Test the rate limiting : Once you’ve set up the rate limiting, you should test it to ensure that it’s working as expected. You can do this by making requests to your API and monitoring the responses to ensure that the rate limiting is being enforced.

Overall, enabling rate limiting in miniOrange API Gateway is a fairly straightforward process that can help you manage the usage of your APIs and prevent abuse or overload.

**For managing Rate Limit, we use the fixed Window method.**

**How does the Fixed Window Rate Limiting Algorithm work?**.

The Fixed Window Rate Limiting Algorithm is a simple algorithm that is commonly used for limiting the rate of requests to a server or API. The algorithm works by allowing a fixed number of requests within a given time window, and rejecting any requests that exceed that limit.

**Here is how the algorithm works**

- Define the maximum number of requests allowed within a given time window, which is typically expressed as requests per second, minute, or hour.
- Define a fixed time window over which to count the number of requests. For example, a window of 1 minute means that the rate limit applies to a maximum number of requests over the previous 60 seconds.
- Keep track of the number of requests made within the time window.
- When a new request is received, check if the number of requests made within the time window has exceeded the maximum allowed. If it has, reject the request. If it has not, allow the request and increment the request counter.
- When the time window expires, reset the request counter to zero and start counting again.

For example, suppose we set the maximum number of requests to 100 per minute. The algorithm will allow up to 100 requests in any 60-second time window. If a request arrives when there have already been 100 requests in the previous 60 seconds, the algorithm will reject the request. If there have been fewer than 100 requests in the previous 60 seconds, the algorithm will allow the request and increment the request counter.
The Fixed Window Rate Limiting Algorithm is a simple but effective way to prevent a system from being overloaded with too many requests. However, it can lead to bursty traffic if requests arrive in large groups during the time window, which can be mitigated by using other rate-limiting algorithms that smooth the traffic more effectively.

### Further Reading {#additional-resources}

- [API Gateway](https://apisecurity.miniorange.in/)

API rate limits safeguard APIs from excessive usage and ensure fair access for all users. These limits define the maximum requests allowed within a specified time frame, preventing server overload and ensuring optimal API performance.

How does rate limiting work to protect APIs from DOS attacks?



## Threat to G-Suite apps?

G Suite applications face a huge threat of data breach if IP restriction is not enabled. Since G Suite applications can be accessed anywhere, at any time, and on any device by any user of an organization (depending on access control) it has attracted the attention of hackers who are constantly trying to exploit the bugs present in the G Suite apps to access company sensitive data. This sensitive data is prone to attacks and constant threats of data leaks. So how can you secure G Suite apps? G Suite apps can be secured from unauthorized user access by setting up IP restrictions with a reverse proxy server. First, let’s see what is IP restriction?


### What is IP restriction? {#what-is-ip-restriction}

IP restriction simply means, to restrict access to something on the basis of the IP addresses. By enabling IP restriction, only certain admin users and other users will have access control for the cloud application (such as G Suite apps) to be protected. IP restriction allows a company’s organization to prevent access to files and folders, from any user whose IP address has not been whitelisted. So IP restriction becomes an incredible security feature to prevent unauthorized access and set user access control for company resources.

With a reverse proxy server, you can set G Suite IP restriction to set access control to your Google apps based on the whitelisted IP addresses. This way you can restrict users by IP and prevent unauthorized access with Google Workspace IP restriction (G Suite IP Whitelist).

Google Workspace IP restriction rules allow your organization’s admin to allow or restrict access to certain IP addresses or an entire range of IP addresses. This way an organization can secure their data from unauthorized, unregistered, and public users on a foreign network from accessing their personnel and business-related data stored on G Suite apps by enabling IP restriction with reverse proxy. A point to be noted about [Google Workspace IP restriction](https://www.miniorange.in/reverse-proxy/google-workspace-account-security), this security feature can be implemented for individual G Suite apps as well. Meaning, you can individually set access control and restrict access to google sheets, docs, slides, etc as per admin and company needs. The most prevalent in-use example of G Suite IP restriction is that of creating security groups for Google Data Studio. In this case, the admin can configure and whitelist IP addresses that should be allowed access to the Google Data Studio according to user groups that need it. The admin can later also configure the access control settings and remove the group as per the company’s needs or add another group of IP addresses at the same time.

### TOP 5 benefits of enabling IP restriction to secure G Suite apps, with a reverse proxy server: {#benefits}

**1.** Prevent access from any user on a foreign network.

**2.** Monitor traffic and check where the access requests come from.

**3.** Restrict an entire range of IP addresses of users with Google Workspace IP Restriction.

**4.** You can also enter specific IP addresses of certain users from accessing G Suite apps.

**5.** No need to install third-party software for user authentication.


### Implementing Google Workspace IP restriction. {#implementing}

Let’s see how Google Workspace IP restriction works with an example,

Let’s say a company is using G Suite Apps for their daily information workflow. The company has enabled IP restriction with a reverse proxy and has whitelisted all the IP address ranges for the company network.

**Suppose there are 2 users:** Jayden and Lexi in the organization. Jayden is on the company network and Lexi is not on the company network. A reverse proxy can be configured to allow or block users with Google workspace IP restriction.

Since Jayden is on the company network, his IP address will be whitelisted by the reverse proxy server. Hence, he will be authorized to use the G Suite apps. Since Lexi is not on the company network, her IP address will not be whitelisted by the reverse proxy server. Hence, she will not be authorized to access any of the Google Workspace apps.

![bot traffic for without reverse proxy](/blog/assets/2023/reverse-proxy-network-g-suite.webp)

### In Summary {#conclusion}

Reverse Proxy is the best practice that allows you to set access control over applications (like Google Workspace) by enabling IP restriction. We can configure which IP address from a particular network should gain (or be denied) access, in order to secure Google Workspace apps (G Suite) and prevent unauthorized access requests from devices operating on a foreign network.

This way you can easily secure your Google Business and Google education apps to provide the most effective security and productive environment for your group.

So what are you waiting for? Drop us a query at [proxysupport@xecurify.com](mailto:proxysupport@xecurify.com) and we will get right back to you to address all your needs.

### Reference links  {#reference-links}

1. [1. Gmail Group Based Access Control With Google Workspace CASB.](https://www.miniorange.in/blog/gmail-group-based-access-control-with-google-workspace-casb/)
2. [2. MS-365 CASB for Microsoft Teams Security.](https://www.miniorange.in/blog/ms-365-casb-for-microsoft-teams-security/)





Google Workspace apps (formerly known as G Suite apps), is a collection of an entire set of productivity apps, such as Google Drive, Docs, Sheets, Slides, Gmail, Google Meet, Google Classroom, etc, which are used by companies, enterprises, universities, schools, and many more, on a daily basis to collaborate on, share, store and edit data of the organization by setting individual or group user access control for the best G Suite security practice.

How to set up WordPress role based access control to secure site folders?

How does rate limiting work to protect APIs from DOS attacks?

How to secure G-Suite apps with IP restriction?