Skip to content

Commit

Permalink
IGNITE-21542 Add documentation on Ignite Security Model (#11277)
Browse files Browse the repository at this point in the history
  • Loading branch information
oleg-vlsk committed May 14, 2024
1 parent a3e24d1 commit 7b8b4ba
Show file tree
Hide file tree
Showing 2 changed files with 23 additions and 1 deletion.
4 changes: 3 additions & 1 deletion docs/_data/toc.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -472,7 +472,9 @@
url: tools/index-reader
- title: Security
url: security
items:
items:
- title: Security Model
url: security/security-model
- title: Authentication
url: security/authentication
- title: SSL/TLS
Expand Down
20 changes: 20 additions & 0 deletions docs/_docs/security/security-model.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
// Licensed to the Apache Software Foundation (ASF) under one or more
// contributor license agreements. See the NOTICE file distributed with
// this work for additional information regarding copyright ownership.
// The ASF licenses this file to You under the Apache License, Version 2.0
// (the "License"); you may not use this file except in compliance with
// the License. You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
= Security Model

When it comes to Apache Ignite security, it is very important to note that by having access to any Ignite cluster node (a server node or a thick client node) it is possible to perform malicious actions on the cluster. There are no mechanisms that could provide protection for the cluster in such scenarios.

Therefore, all link:../clustering/network-configuration.adoc#_discovery[Discovery] and link:../clustering/network-configuration.adoc#_communication[Communication] ports for Ignite server and thick client nodes should only be available inside a protected subnetwork (the so-called demilitarized zone or DMZ). Should those ports be exposed outside of DMZ, it is advised to control access to them by using SSL certificates issued by a trusted Certification Authority (please see this link:ssl-tls.adoc[page] for more information on Apache Ignite SSL/TLS configuration).

0 comments on commit 7b8b4ba

Please sign in to comment.