Vault7: CIA Hacking Tools Revealed
Navigation: » Directory » Network Devices Branch (NDB)
Owner: User #1179825
Network Devices Branch
Our Daily Tip
Comments:
-
2015-03-27 06:53 [User #14587667]:
Thank you for the valuable information. This helps alot.
-
2015-03-23 12:40 [User #524297]:
Could you please create an NDBNetwork Devices Branch 'group' in JIRAUser Managment Software (Atlassian) and under that create a project called 'HunGrrr'. Also, is it possible to create an NDBNetwork Devices Branch group for Confluence (and JIRAUser Managment Software (Atlassian) if possible)? We need the ability to restrict viewing/editing of certain pages, and would like to do at the group level (rather than adding 12 teams members to every page). Thanks, User #73928User #73929, I found this in Jira, in the area where EIB(Branch) was testing a Service Desk plugin (which I don't think that EIB(Branch) will adopt).
- So because NDBNetwork Devices Branch is part of ESD, all the permissions for the Atlassian applications are meted out manually (because not every ESD(Branch) branch will use every application). So you are on the right track.
- I have given all of NDBNetwork Devices Branch user accesses they will need for Jira.
- This will not allow the creation of a project. I have given you specifically project creation/administrator privileges. So you can create projects, but not anyone else (unless you assign a project to them). If you run into problems, let me know.
- There is already a security group for NDBNetwork Devices Branch that is part of the DEVLAN Active Directory, and it is
sg-NDB
. So you can use this as a group for permissions.- HOWEVER – I would caution you about restricting access. You can restrict some writing/editing permissions at the Space Level (see the "Space tools" gear in the lower left corner) which may accomplish what you want (e.g. preventing mischief).
- If you are planning on putting Restricted Handling or sensitive operational data into Confluence, consider that there are multiple people with administrator privileges, and that DEVLAN is not approved for RH/HCS (even though it was for HCS at one point regardless of what EIB(Branch) says).
- So because NDBNetwork Devices Branch is part of ESD, all the permissions for the Atlassian applications are meted out manually (because not every ESD(Branch) branch will use every application). So you are on the right track.
-
2015-02-09 09:07 [User #14587667]:
Test verified (really I'm just trying to rack up points)
-
2015-01-15 14:21 [User #1179825]:
Testing the comments field.
Sub-Pages:
- NDB Test Range Task Report
- Push-up Tracker
- How-to articles
- Tool Quick Start Guides empty
- Archive empty
- Test Range Notes
- Meeting notes
- Operations/Testing
- Test Range Infrastructure
- Lab Notes
- Lab Demonstrations
- Lab Infrastructure
Previous versions:
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 |