The technique of k-anonymization has been proposed in the literature as an alternative way to release public information, while ensuring both data privacy and data confidentiality. “X” owns a k-anonymous database and needs to determine whether “X” database, when inserted with a tuple owned by “Y”, is still k-anonymous. Clearly, allowing “X” to directly read the contents of the tuple breaks the privacy of “Y”. In this place,”Y” not get the privacy of own information because the information of “Y” can be accessed by “X” without the prior knowledge of “Y”. On the other hand, the confidentiality of the database managed by “X” is violated once “Y” has access to the contents of database. Thus, the problem is to check whether the database inserted with the tuple is still k-anonymous, without letting “X” and “Y” knows the contents of the tuple and database respectively. In this paper, we propose two protocols solving this problem that is suppression-Based & Generalization-Based k-anonymous and confidential databases using through prototype architecture. And also those two protocols maintain privacy and confidential information in k-anonymous database.