Anonymous, bureaucrat, administrator
7,528
edits
Changes
From All n One's bxp software Wixi
no edit summary
= Overview =
{| class="wikitable" style="width:100%;"
! style="width:20%;" | Overview
! style="width:20%;" | Retrieve
! style="width:20%;" | Input
! style="width:20%;" | Process
! style="width:20%;" | Output
|-
| style="text-align:center;" | [[MetaData_-_Start_Here|Link]]
| style="text-align:center;" | [[MetaData_-_Retrieve|Link]]
| style="text-align:center;" | [[MetaData_Process_Input|Link]]
| style="text-align:center;" | [[MetaData_Process_Rules|Link]]
| style="text-align:center;" | [[MetaData_Process_Output|Link]]
|-
|}
Retrieving data from various sources is the first step in a MetaData process. There are various options to how data can be brought into bxp. This article discusses the various options and approaches used.
* Pull: bxp must go into another system and pull out the data
* Push: An external system pushes the data into bxp
There are different times where these approaches are appropriate . The primary deciding factor is the primary considerations are of associated security. If securityof the remote client is paramount, all solutions suggested will tend to be Push. This allows the client to dictate the hows and when bxp gets the data.
If security of the remote client is paramount, all solutions suggested will be Push. This allows the client to dictate the hows and when bxp gets its data. If comfortable with their security measures are in place, bxp can log in to retrieve data. This is usually through one of three methods.
* SFTP file retrieval
Where API interaction is required, the API documentation is supplied by the client and a connector is appropriately built. SOAP, XML, JSON, RESTful, etc are all supported. For security, current client integration examples are not listed here.
bxp to retain its high availability cannot does not VPN into client infrastructures. VPN connections and their maintenance across the nTier of our web platform is unsustainable and can be easily replaced with PUSH sFTP solutions. Which All n One can provide support on.
* The primary bxp interface: Over HTTPS a user can upload files into a bxp system
* All n One email account: All n One can provide an @allnone.ie email address external to the clients environment which bxp can retrieve emails and attachments from
Once the files are within bxp, again decryption of encrypted content can be performed.
= VPN =
A Virtual Private Network, creates a bubble which extends the security of your internal network out and around another machine on another network.
VPNs are a massive security consideration. They also offer allow a number of capabilities not possible with other solutions. Consider two networks.
[[File:metadata_retrieve_001.png|400px]]
The base interactions described above are tried, tested, secured and checked protocols for interaction. So the security tends to interact at the edge points.
[[File:metadata_retrieve_002.png|400px]]
In a VPN scenario, a machine, or even an entire network enters a security bubble
[[File:metadata_retrieve_003.png|400px]]
A VPN is a two way street. If the machine enters a network, machines on that network can chat. For this reason it is not possible to put a production web server of bxp into another clients network for security reasons. Instead a staging / intermediate server is required, controlled and security audited.
[[File:metadata_retrieve_004.png|400px]]
Now the files can be retrieved from the VPN and then presented securely to bxp through one of the secured interfaces.
= Audit-ability =
The primary concern for any security department is to be able to audit any process especially in the transfer of data. Numerous auditing reports and details are supported [[Bxp_-_Audit_Logs]]
