IP rules to access Autonomous Database-Shared

IP rules to access Autonomous Database-Shared


As a database administrator or manager, you may have had one or more of these conversations with your application teams.

"We need to build a new mobile app so customers can submit and retrieve documents, so I will need a specialized database to store the documents, right?

Oh, wait, next week, this other project requires we provide a new payment system with user fraud protection built in to meet compliance, and I am going to store relational data as well. We’ll need a specialized Blockchain database and a relational database, right?"

These conversations can leave you concerned and frustrated, wondering how you will allocate your resources to these specialized data stores.

But perhaps the solution to your problem is not more resources but a Converged Database.

A Converged Database is a database that has native support for all modern data types, analytics, and the latest development paradigms built into one product.

That's where Autonomous Database comes into the picture.

But now as a security expert how can you make sure if your application data is not shared within the one single database.

IP filtering is one option that can be used to block traffic from specific IP addresses, protect against unauthorized network access and manage access to content. All this can be done from the Database too, leaving out the network admin.

Here's how its done.

https://blogs.oracle.com/database/post/using-ip-rules-to-access-autonomous-database-shared


To view or add a comment, sign in

More articles by Goutam Pal

Explore content categories